delete_gtm_trigger

Delete a trigger from a GTM workspace (draft, not published). Applies the audit fix for an unused trigger. Destructive, requires two confirmations.

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-gtm-trigger.md

WHAT IT DOES

What delete_gtm_trigger does on Samarth Gtm Mcp

AI agents call delete_gtm_trigger 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.

RISK

Why delete_gtm_trigger is rated Critical

Irreversibly removes GTM trigger configuration; cannot be undone without manual recreation.

From the tool's definition Delete a trigger from a GTM workspace. Destructive, requires two confirmations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_gtm_trigger 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_trigger, this is the rule to start with:

delete_gtm_trigger Hidden

delete_gtm_trigger is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_gtm_trigger"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Samarth Gtm Mcp, apply this rule, and every delete_gtm_trigger call is checked against it from then on.

FAQ

Questions about delete_gtm_trigger

What does the delete_gtm_trigger tool do? +

Delete a trigger from a GTM workspace (draft, not published). Applies the audit fix for an unused trigger. 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.

How do I enforce a policy on delete_gtm_trigger? +

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

delete_gtm_trigger 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_gtm_trigger? +

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

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

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

KEEP EXPLORING

More on Samarth Gtm, and thousands of servers like it.

This server

All 236 Samarth Gtm tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →