diff --git a/docs/modules/maintain-cluster/pages/monitoring.adoc b/docs/modules/maintain-cluster/pages/monitoring.adoc
index 585334c9c..85bd5e0a5 100644
--- a/docs/modules/maintain-cluster/pages/monitoring.adoc
+++ b/docs/modules/maintain-cluster/pages/monitoring.adoc
@@ -91,6 +91,11 @@ Management Center allows you to execute scripts that can automate interactions w
 
 By default, scripting is disabled for security. Scripting engines give code access to the underlying system on the members (files and other resources) and run with the same permissions as the current user. You can enable scripting in the member configuration file:
 
+[IMPORTANT]
+====
+When scripting is enabled, it grants full, unrestricted access to the cluster and is *not* limited by the permissions assigned to individual Management Center users. Enable it with caution, especially in production, and consider leaving it disabled if granular access control is critical. See the xref:{page-latest-supported-mc}@management-center:tools:scripting.adoc[Management Center scripting documentation] for details.
+====
+
 [tabs] 
 ==== 
 XML:: 
@@ -122,6 +127,11 @@ Note that the https://jcp.org/en/jsr/detail?id=223[JSR 223^] API is used in Haze
 
 Management Center allows you to execute client operations using built-in Hazelcast Command-Line Client (CLC) in the user interface. This console is useful for testing and development purposes. You can enable the console in the member configuration file:
 
+[IMPORTANT]
+====
+When the console is enabled, it grants full access to the cluster through the Command-Line Client and is *not* limited by the permissions assigned to individual Management Center users. Enable it with caution, especially in production, and consider leaving it disabled if granular access control is critical.
+====
+
 [tabs] 
 ==== 
 XML::