New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

triggers_delete

[DELETE] Delete a GTM trigger. Requires GTM_MCP_ENABLE_DELETES=true and confirm=true.

SERVERSamarth Gtm Mcp SOURCEsamarth-gtm-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

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…

Questions about triggers_delete

What does the triggers_delete tool do? +

[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.

How do I enforce a policy on triggers_delete? +

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.

What risk level is triggers_delete? +

triggers_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit triggers_delete? +

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.

How do I block triggers_delete completely? +

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.

What MCP server provides triggers_delete? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Samarth Gtm's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.