gtm_container

THE RISK

Critical Risk

The tool includes 'remove' which is an irreversible destructive operation on GTM containers. Since the tool bundles multiple operations including destructive ones, and per the rules we pick the most severe applicable category, this classifies as Destructive. Misuse could delete entire GTM containers affecting tracking and analytics across potentially many websites, hence high severity.

From the tool's definition Performs all container-related operations: create, get, update, remove, list, combine, lookup, moveTagId, snippet

Documented attack patterns abuse exactly the kind of access gtm_container gives an agent:

HOW TO CONTROL GTM_CONTAINER

PolicyLayer is an MCP gateway — it sits between your AI agents and Google Tag Manager MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for gtm_container:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "gtm_container"
  ]
}

gtm_container disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Google Tag Manager MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

More Google Tag Manager MCP Server tools

Destructive gtm_built_in_variable Performs all built-in variable operations: create, list, remove, revert. The Destructive gtm_client Performs all client operations: create, get, list, update, remove, revert. The Destructive gtm_environment Performs all environment operations: create, get, list, update, remove, reauthorize. The Destructive gtm_folder Performs all folder operations: create, get, list, update, remove, revert, entities, moveE Destructive gtm_gtag_config Performs all Google tag config operations: create, get, list, update, remove. The Destructive gtm_tag Performs all GTM tag operations: create, get, list, update, remove, revert. The Destructive gtm_template Performs all GTM custom template operations: create, get, list, update, remove, revert. Th Destructive gtm_transformation Performs all GTM transformation operations: create, get, list, update, remove, revert. The

All 18 Google Tag Manager MCP Server tools →

Destructive tools on other servers

Frida Game Hacking MCP clear_scan MegaMemory remove_concept Frida Agent MCP kill_app 1MCP Server mcp_uninstall

Go deeper

Critical-risk tools in Google Tag Manager MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the gtm_container tool do? +

Performs all container-related operations: create, get, update, remove, list, combine, lookup, moveTagId, snippet. The. 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.

How do I enforce a policy on gtm_container? +

Register the Google Tag Manager MCP Server MCP server in PolicyLayer and add a rule for gtm_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 Google Tag Manager MCP Server. Nothing to install.

What risk level is gtm_container? +

gtm_container 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_container? +

Yes. Add a rate_limit block to the gtm_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.

How do I block gtm_container completely? +

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

What MCP server provides gtm_container? +

gtm_container is provided by the Google Tag Manager MCP Server MCP server (stape-io/google-tag-manager-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Google Tag Manager MCP Server tool call.

Deterministic rules across all 18 Google Tag Manager MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN GOOGLE TAG MANAGER →

Free to start. No card required.

18 Google Tag Manager MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// WHAT GTM_CONTAINER ON GOOGLE TAG MANAGER MCP SERVER DOES

// THE RISK

// HOW TO CONTROL GTM_CONTAINER

// EXPLORE