Performs workspace operations: get, list, create, update, delete.
AI agents call gtm_workspace 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.
Although the tool encompasses read (get, list), write (create, update), and destructive (delete) operations, the delete capability makes it Destructive per the classification rules. Deleting a GTM workspace would irreversibly remove configuration, tags, triggers, and variables associated with that workspace, potentially disrupting tracking and marketing infrastructure.
From the tool's definition Tool description explicitly states 'get, list, create, update, delete' operations on workspaces in Google Tag Manager, with delete capability being irreversible.
Attacks that exploit this kind of access
Performs workspace operations: get, list, create, update, delete. 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 gtm_workspace: 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.
gtm_workspace 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_workspace 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_workspace. 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_workspace is provided by the Google Tag Manager MCP Server MCP server (metkamedia/gtm-mcp-server). 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 →