triggers_delete
[DELETE] Delete a GTM trigger. Requires GTM_MCP_ENABLE_DELETES=true and confirm=true.
This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/triggers-delete.md
What triggers_delete does on Samarth Gtm Mcp
AI agents call triggers_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 triggers_delete is rated Critical
This tool irreversibly deletes GTM trigger configurations. Unlike reversible Write operations, trigger deletion cannot be undone and removes active tracking/measurement infrastructure. The high severity reflects the potential impact: a misconfigured AI agent could delete critical tracking triggers, breaking analytics instrumentation.
From the tool's definition Tool name contains '[DELETE]' and description states 'Delete a GTM trigger'. The description explicitly mentions this is a destructive operation that requires environment flag GTM_MCP_ENABLE_DELETES=true and confirmation, indicating irreversible removal of…
Attacks that exploit this kind of access
The rule that runs triggers_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 triggers_delete, this is the rule to start with:
triggers_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 triggers_delete call is checked against it from then on.
Questions about triggers_delete
[DELETE] Delete a GTM trigger. 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 triggers_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.
triggers_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 triggers_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 triggers_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.
triggers_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