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

delete_unused_gtm_triggers

Bulk-delete the UNUSED (orphaned) triggers in a GTM workspace: referenced by no tag (firing or blocking) and not a Trigger Group member. By DEFAULT deletes ALL unused ones; pass triggerIds to delete only those, and any id actually in use or not found is skipped and reported, NEVER deleted. Prefer...

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/delete-unused-gtm-triggers.md

What delete_unused_gtm_triggers does on Samarth Gtm Mcp

AI agents call delete_unused_gtm_triggers 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_triggers is rated Critical

Permanently deletes GTM triggers without recovery option, with safeguards but remains destructive operation.

From the tool's definition Bulk-delete the UNUSED GTM triggers irreversibly; Destructive, confirms twice

Questions about delete_unused_gtm_triggers

What does the delete_unused_gtm_triggers tool do? +

Bulk-delete the UNUSED (orphaned) triggers in a GTM workspace: referenced by no tag (firing or blocking) and not a Trigger Group member. By DEFAULT deletes ALL unused ones; pass triggerIds to delete only those, and any id actually in use or not found is skipped and reported, NEVER deleted. Prefer list_unused_gtm_triggers first so the user sees what will go. 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.

How do I enforce a policy on delete_unused_gtm_triggers? +

Register the Samarth Gtm MCP server in PolicyLayer and add a rule for delete_unused_gtm_triggers: 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 delete_unused_gtm_triggers? +

delete_unused_gtm_triggers 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 delete_unused_gtm_triggers? +

Yes. Add a rate_limit block to the delete_unused_gtm_triggers 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 delete_unused_gtm_triggers completely? +

Set action: deny in the PolicyLayer policy for delete_unused_gtm_triggers. 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 delete_unused_gtm_triggers? +

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