gtm_workspace

Performs various workspace operations including create, get, list, update, remove, createVersion, getStatus, sync, quickPreview, and resolveConflict actions. The

Server Unboundai Gtm tijevlam/unboundai-google-tag-manager-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What gtm_workspace does on Unboundai Gtm

AI agents call gtm_workspace to permanently remove resources in Unboundai Gtm — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why gtm_workspace needs a policy

The tool spans multiple categories but includes 'remove' (irreversible deletion of a workspace) and 'resolveConflict' (overwrites conflicting changes), which are destructive. Per the rules, the most severe applicable category wins: Destructive > Execute > Write > Read. 'remove' on a GTM workspace can permanently delete unpublished work and configurations, making the blast radius high if misused by an AI agent.

From the tool's definition operations including create, get, list, update, remove, createVersion, getStatus, sync, quickPreview, and resolveConflict actions

Questions about gtm_workspace

What does the gtm_workspace tool do? +

Performs various workspace operations including create, get, list, update, remove, createVersion, getStatus, sync, quickPreview, and resolveConflict actions. The. It is categorised as a Destructive tool in the Unboundai Gtm 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 gtm_workspace? +

Register the Unboundai Gtm 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 Unboundai Gtm. Nothing to install.

What risk level is gtm_workspace? +

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

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.

How do I block gtm_workspace completely? +

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.

What MCP server provides gtm_workspace? +

gtm_workspace is provided by the Unboundai Gtm MCP server (tijevlam/unboundai-google-tag-manager-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.