built_in_variables_disable
[DELETE] Disable one or more built-in variables in a GTM workspace.
This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/built-in-variables-disable.md
What built_in_variables_disable does on Samarth Gtm Mcp
AI agents call built_in_variables_disable to permanently remove resources in Samarth Gtm Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why built_in_variables_disable is rated Critical
The [DELETE] prefix and 'disable' action indicate this tool removes/disables built-in variables in a GTM workspace. Disabling built-in variables in GTM can break tracking configurations across a container, and this action may not be easily reversible if dependent tags and triggers rely on those variables. This qualifies as Destructive given the potential irreversible impact on GTM container configurations.
From the tool's definition [DELETE] Disable one or more built-in variables in a GTM workspace
Attacks that exploit this kind of access
The rule that runs built_in_variables_disable safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Samarth Gtm Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For built_in_variables_disable, this is the rule to start with:
built_in_variables_disable is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Samarth Gtm Mcp, apply this rule, and every built_in_variables_disable call is checked against it from then on.
Questions about built_in_variables_disable
[DELETE] Disable one or more built-in variables in a GTM workspace. It is categorised as a Destructive tool in the Samarth Gtm Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Samarth Gtm MCP server in PolicyLayer and add a rule for built_in_variables_disable: 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 Samarth Gtm Mcp. Nothing to install.
built_in_variables_disable is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the built_in_variables_disable 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 built_in_variables_disable. 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.
built_in_variables_disable is provided by the Samarth Gtm MCP server (samarth-gtm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Samarth Gtm, and thousands of servers like it.
Across the catalogue