Delete (archive) a container version. The version can be restored later.
AI agents call gtm_delete_version to permanently remove resources in Gtm — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool deletes/archives a GTM container version, which is an irreversible action that destroys the current state of that version. Although restoration is possible, the deletion itself is a destructive operation that could break live tag deployments or remove critical tracking configurations. The blast radius is significant in a GTM context as it affects analytics, advertising, and user tracking infrastructure.
From the tool's definition Tool name and description explicitly state 'Delete (archive) a container version.' The action removes a version from the container, even though it notes the version 'can be restored later,' the primary operation is irreversible deletion.
Attacks that exploit this kind of access
Delete (archive) a container version. The version can be restored later. It is categorised as a Destructive tool in the Gtm MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Gtm MCP server in PolicyLayer and add a rule for gtm_delete_version: 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 Gtm. Nothing to install.
gtm_delete_version 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 gtm_delete_version 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 gtm_delete_version. 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.
gtm_delete_version is provided by the Gtm MCP server (tijevlam/gtm-mcp). 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 →