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...
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
Attacks that exploit this kind of access
The rule that runs delete_unused_gtm_triggers 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_triggers, this is the rule to start with:
delete_unused_gtm_triggers 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_triggers call is checked against it from then on.
Questions about 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 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.
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.
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.
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.
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.
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.
Across the catalogue