googleTagManager_delete_container
Delete a GTM container
This record as markdown: /tools/io-github-alifanov-scopegate/googletagmanager-delete-container.md
What googleTagManager_delete_container does on ScopeGate
AI agents call googleTagManager_delete_container 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_container is rated Critical
Deleting a GTM container permanently removes all associated tracking tags, triggers, and configuration—an operation that cannot be undone without restoration from backups. This is a destructive action affecting business analytics infrastructure.
From the tool's definition Tool name explicitly states 'delete_container' and description is 'Delete a GTM container'. The verb 'delete' combined with 'container' (a data structure holding configuration, tags, triggers, variables) indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs googleTagManager_delete_container safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For googleTagManager_delete_container, this is the rule to start with:
googleTagManager_delete_container is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect ScopeGate, apply this rule, and every googleTagManager_delete_container call is checked against it from then on.
Questions about googleTagManager_delete_container
Delete a GTM container. 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.
Register the ScopeGate MCP server in PolicyLayer and add a rule for googleTagManager_delete_container: 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.
googleTagManager_delete_container 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 googleTagManager_delete_container 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 googleTagManager_delete_container. 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.
googleTagManager_delete_container 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.
Across the catalogue