delete_gtm_tag
Delete a tag from a GTM workspace (draft, not published). Destructive, requires two confirmations.
This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/delete-gtm-tag.md
What delete_gtm_tag does on Samarth Gtm Mcp
AI agents call delete_gtm_tag 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_gtm_tag is rated Critical
Irreversibly removes GTM tags; cannot be undone without manual recreation. Requires confirmations but remains destructive.
From the tool's definition Delete a tag from a GTM workspace (draft, not published). Destructive.
Attacks that exploit this kind of access
The rule that runs delete_gtm_tag 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_gtm_tag, this is the rule to start with:
delete_gtm_tag 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_gtm_tag call is checked against it from then on.
Questions about delete_gtm_tag
Delete a tag from a GTM workspace (draft, not published). Destructive, requires two confirmations. 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_gtm_tag: 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_gtm_tag 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_gtm_tag 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_gtm_tag. 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_gtm_tag 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