googleTagManager_delete_environment
Delete a GTM environment
This record as markdown: /tools/io-github-alifanov-scopegate/googletagmanager-delete-environment.md
What googleTagManager_delete_environment does on ScopeGate
AI agents call googleTagManager_delete_environment 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_environment is rated Critical
The tool irreversibly removes a GTM environment, which constitutes destructive action. The severity is high rather than critical because the blast radius is scoped to a single GTM property's environment rather than all data or financial systems, but deletion of tracked configurations could break analytics and tracking infrastructure if triggered inadvertently. Confidence is high because the intent is unambiguous.
From the tool's definition Tool name explicitly contains 'delete_environment'; description states 'Delete a GTM environment'. GTM (Google Tag Manager) environments are configuration states that, once deleted, cannot be recovered without manual recreation.
Attacks that exploit this kind of access
The rule that runs googleTagManager_delete_environment 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_environment, this is the rule to start with:
googleTagManager_delete_environment 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_environment call is checked against it from then on.
Questions about googleTagManager_delete_environment
Delete a GTM environment. 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_environment: 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_environment 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_environment 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_environment. 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_environment 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