Delete GTM configuration by ID
AI agents call delete_gtm_config to permanently remove resources in Google Tag Manager MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of GTM configurations cannot be undone and removes tracking setup that may be critical to business operations. This is a destructive action with potentially broad impact on analytics and marketing infrastructure. While not financial in itself, its misuse could disable revenue-tracking systems.
From the tool's definition Tool name 'delete_gtm_config' and description 'Delete GTM configuration by ID' explicitly perform deletion of Google Tag Manager configurations, which is irreversible.
Attacks that exploit this kind of access
Delete GTM configuration by ID. It is categorised as a Destructive tool in the Google Tag Manager MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google Tag Manager MCP Server MCP server in PolicyLayer and add a rule for delete_gtm_config: 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 Google Tag Manager MCP Server. Nothing to install.
delete_gtm_config 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_gtm_config 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_gtm_config. 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_gtm_config is provided by the Google Tag Manager MCP Server MCP server (neep305/mcp-for-gtm). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →