save_gtm_config · Google Tag Manager MCP Server MCP

WHAT IT DOES

What save_gtm_config does on Google Tag Manager MCP Server

AI agents use save_gtm_config to create or update resources in Google Tag Manager MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Tag Manager MCP Server environment.

WHY IT NEEDS A POLICY

Why save_gtm_config needs a policy

The tool writes/persists Google Tag Manager configurations to a database. This is a Write category tool because it creates or modifies data reversibly. Severity is high because misconfigured GTM tags could result in tracking data corruption, privacy violations (unintended data collection), or ecommerce transaction tracking failures that affect business operations, though the effects are typically recoverable by…

From the tool's definition Tool name 'save_gtm_config' and description 'Save GTM configuration to database' indicate data persistence via write operation. The tool creates or modifies GTM configurations in a database, which is a reversible write action.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

save_gtm_config Rate-limited

save_gtm_config 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": {
    "save_gtm_config": {
      "limits": [
        {
          "counter": "save_gtm_config_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 Google Tag Manager MCP Server, so you can run agents against it safely.

FAQ

Questions about save_gtm_config

What does the save_gtm_config tool do? +

Save GTM configuration to database. It is categorised as a Write tool in the Google Tag Manager MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on save_gtm_config? +

Register the Google Tag Manager MCP Server MCP server in PolicyLayer and add a rule for save_gtm_config: 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 save_gtm_config? +

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

Can I rate-limit save_gtm_config? +

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

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

save_gtm_config is provided by the Google Tag Manager MCP Server MCP server (neep305/mcp-for-gtm). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.