Performs all account-related operations: get, list, update. Use the
AI agents use gtm_account 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.
While the tool includes read operations (get, list), the 'update' capability makes it a Write tool rather than Read-only. The severity is high because unauthorized account modifications could alter tracking configurations, analytics pipelines, or data collection across an organization's digital properties.
From the tool's definition Tool description states it 'Performs all account-related operations: get, list, update.' The inclusion of 'update' indicates the tool can modify account data.
Documented attack patterns abuse exactly the kind of access gtm_account gives an agent:
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_account:
{
"version": "1",
"default": "deny",
"tools": {
"gtm_account": {
"limits": [
{
"counter": "gtm_account_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}gtm_account 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.
Free to start. No card required.
Performs all account-related operations: get, list, update. Use the. 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.
Register the Google Tag Manager MCP Server MCP server in PolicyLayer and add a rule for gtm_account: 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.
gtm_account is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the gtm_account 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.
Set action: deny in the PolicyLayer policy for gtm_account. 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.
gtm_account 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.
Deterministic rules across all 18 Google Tag Manager MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
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.