gtm_publish_container · Gtm MCP: Risk & Policy

WHAT IT DOES

What gtm_publish_container does on Gtm

AI agents invoke gtm_publish_container to trigger actions in Gtm. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why gtm_publish_container needs a policy

Publishing a GTM container version pushes changes live to production websites, affecting all visitors. This is an external operation with significant real-world impact (modifying what JavaScript/tags run on live sites). While it creates a version (Write), the publish action deploys it externally, making it Execute.

From the tool's definition 'Create and publish a new version of a GTM container' — publishing triggers external deployment of tracking/tag configuration to live web properties

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

gtm_publish_container Rate-limited

gtm_publish_container stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gtm_publish_container": {
      "limits": [
        {
          "counter": "gtm_publish_container_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Gtm, so you can run agents against it safely.

FAQ

Questions about gtm_publish_container

What does the gtm_publish_container tool do? +

Create and publish a new version of a GTM container. It is categorised as a Execute tool in the Gtm MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on gtm_publish_container? +

Register the Gtm MCP server in PolicyLayer and add a rule for gtm_publish_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 Gtm. Nothing to install.

What risk level is gtm_publish_container? +

gtm_publish_container is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit gtm_publish_container? +

Yes. Add a rate_limit block to the gtm_publish_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_publish_container completely? +

Set action: deny in the PolicyLayer policy for gtm_publish_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_publish_container? +

gtm_publish_container is provided by the Gtm MCP server (tijevlam/gtm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.