gtm_update_version · Gtm MCP: Risk & Policy

WHAT IT DOES

What gtm_update_version does on Gtm

AI agents use gtm_update_version to create or update resources in Gtm — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gtm environment.

WHY IT NEEDS A POLICY

Why gtm_update_version needs a policy

This tool modifies existing data in Google Tag Manager by updating container version metadata. The changes are reversible—metadata like names, descriptions, and notes can be edited back to previous states. This makes it a Write operation rather than Destructive.

From the tool's definition Tool description states 'Update metadata of a container version (name, description, notes)'. The verb 'Update' and the reversible nature of metadata changes (name, description, notes can be changed back) classify this as a Write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

gtm_update_version Rate-limited

gtm_update_version stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_update_version": {
      "limits": [
        {
          "counter": "gtm_update_version_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_update_version

What does the gtm_update_version tool do? +

Update metadata of a container version (name, description, notes). It is categorised as a Write tool in the Gtm MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on gtm_update_version? +

Register the Gtm MCP server in PolicyLayer and add a rule for gtm_update_version: 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_update_version? +

gtm_update_version is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit gtm_update_version? +

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

Set action: deny in the PolicyLayer policy for gtm_update_version. 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_update_version? +

gtm_update_version 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.