googleTagManager_delete_variable

Delete a variable from a GTM workspace

SERVERScopeGate SOURCEhttps://mcp.scopegate.cloud/{api_key}
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-alifanov-scopegate/googletagmanager-delete-variable.md

What googleTagManager_delete_variable does on ScopeGate

AI agents call googleTagManager_delete_variable to permanently remove resources in ScopeGate, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why googleTagManager_delete_variable is rated Critical

Deleting a GTM variable is a destructive action that cannot be undone without manual restoration. GTM variables are often critical to tracking configurations, analytics pipelines, and conversion tracking. Unintended deletion could break marketing tracking, disrupt data collection, or cause loss of configuration state. While not directly financial, the blast radius is significant for business operations.

From the tool's definition Tool name contains 'delete' and description states 'Delete a variable from a GTM workspace' — this is an irreversible deletion operation.

Questions about googleTagManager_delete_variable

What does the googleTagManager_delete_variable tool do? +

Delete a variable from a GTM workspace. It is categorised as a Destructive tool in the ScopeGate 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 googleTagManager_delete_variable? +

Register the ScopeGate MCP server in PolicyLayer and add a rule for googleTagManager_delete_variable: 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 ScopeGate. Nothing to install.

What risk level is googleTagManager_delete_variable? +

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

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

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

googleTagManager_delete_variable is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on ScopeGate, 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 ScopeGate'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.