delete_unused_gtm_variables
Bulk-delete the UNUSED (orphaned) variables in a GTM workspace: {{name}} referenced by no tag, trigger or other variable in the readable fields. By DEFAULT deletes ALL unused ones; pass variableIds to delete only those, and any id actually referenced or not found is skipped and reported. Prefer l...
This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/delete-unused-gtm-variables.md
What delete_unused_gtm_variables does on Samarth Gtm Mcp
AI agents call delete_unused_gtm_variables 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 delete_unused_gtm_variables is rated Critical
Irreversibly deletes GTM variables with risk of silent breakage if references exist in unaudited fields.
From the tool's definition Bulk-delete UNUSED variables in GTM workspace, irreversible deletion, cannot be undone.
Attacks that exploit this kind of access
The rule that runs delete_unused_gtm_variables 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 delete_unused_gtm_variables, this is the rule to start with:
delete_unused_gtm_variables 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 delete_unused_gtm_variables call is checked against it from then on.
Questions about delete_unused_gtm_variables
Bulk-delete the UNUSED (orphaned) variables in a GTM workspace: {{name}} referenced by no tag, trigger or other variable in the readable fields. By DEFAULT deletes ALL unused ones; pass variableIds to delete only those, and any id actually referenced or not found is skipped and reported. Prefer list_unused_gtm_variables first. CAUTION: unlike triggers, the GTM API does NOT refuse to delete a REFERENCED variable, and this detection is a hint, not proof: a variable used only in a published version, or in a field the audit cannot read, could be wrongly deleted, silently breaking that {{reference}}. Destructive, confirms twice. 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 delete_unused_gtm_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 Samarth Gtm Mcp. Nothing to install.
delete_unused_gtm_variables 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 delete_unused_gtm_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 delete_unused_gtm_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.
delete_unused_gtm_variables 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