New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

versions_delete

[DELETE] Delete a GTM container version.

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/versions-delete.md

What versions_delete does on Samarth Gtm Mcp

AI agents call versions_delete 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 versions_delete is rated Critical

This tool permanently deletes GTM container versions, which cannot be undone. Despite the server description claiming 'read-only by default, gated writes, audits', this tool performs destructive operations on GTM configuration history. The deletion of container versions is irreversible and could impact tracking configuration integrity. Even with gates and audits, the capability itself is destructive.

From the tool's definition Tool name contains 'delete', description explicitly states '[DELETE] Delete a GTM container version', indicating irreversible removal of a versioned artifact.

Questions about versions_delete

What does the versions_delete tool do? +

[DELETE] Delete a GTM container version. 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 versions_delete? +

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

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

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

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

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

// 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 Samarth Gtm'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.