googleTagManager_list_built_in_variables
List all enabled built-in variables in a GTM workspace
This record as markdown: /tools/io-github-alifanov-scopegate/googletagmanager-list-built-in-variables.md
What googleTagManager_list_built_in_variables does on ScopeGate
AI agents call googleTagManager_list_built_in_variables to retrieve information from ScopeGate without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why googleTagManager_list_built_in_variables is rated Low
This tool performs a read-only operation to enumerate GTM built-in variables. It has no side effects, does not execute code, and does not modify data. The blast radius of misuse is minimal — an agent could learn about available variables but cannot change configurations, execute tags, or access sensitive data beyond variable metadata. Classified as Read with low severity.
From the tool's definition Tool name contains 'list' and description states 'List all enabled built-in variables' — a query operation that retrieves information about GTM workspace configuration without modifying or executing anything.
Attacks that exploit this kind of access
The rule that runs googleTagManager_list_built_in_variables safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For googleTagManager_list_built_in_variables, this is the rule to start with:
googleTagManager_list_built_in_variables is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ScopeGate, apply this rule, and every googleTagManager_list_built_in_variables call is checked against it from then on.
Questions about googleTagManager_list_built_in_variables
List all enabled built-in variables in a GTM workspace. It is categorised as a Read tool in the ScopeGate MCP Server, which means it retrieves data without modifying state.
Register the ScopeGate MCP server in PolicyLayer and add a rule for googleTagManager_list_built_in_variables: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches ScopeGate. Nothing to install.
googleTagManager_list_built_in_variables is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the googleTagManager_list_built_in_variables rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for googleTagManager_list_built_in_variables. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
googleTagManager_list_built_in_variables is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScopeGate, and thousands of servers like it.
This server
Across the catalogue