variables_delete
[DELETE] Delete a GTM variable. Requires GTM_MCP_ENABLE_DELETES=true and confirm=true.
This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/variables-delete.md
What variables_delete does on Samarth Gtm Mcp
AI agents call variables_delete 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 variables_delete is rated Critical
This tool performs irreversible deletion of GTM variables. Although gated behind environment variable GTM_MCP_ENABLE_DELETES=true and a confirmation parameter, deletion operations that cannot be undone fall into the Destructive category, which outranks Write.
From the tool's definition Tool name is 'variables_delete' with description '[DELETE] Delete a GTM variable.' The DELETE operation irreversibly removes a GTM variable configuration, which cannot be undone without restoration from backups.
Attacks that exploit this kind of access
The rule that runs variables_delete 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 variables_delete, this is the rule to start with:
variables_delete 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 variables_delete call is checked against it from then on.
Questions about variables_delete
[DELETE] Delete a GTM variable. Requires GTM_MCP_ENABLE_DELETES=true and confirm=true. 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 variables_delete: 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.
variables_delete 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 variables_delete 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 variables_delete. 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.
variables_delete 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