Performs all container version header operations: list, latest. The
AI agents call gtm_version_header to retrieve information from Google Tag Manager MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The gtm_version_header tool is limited to querying and listing container version headers. It provides informational read access to GTM version metadata without creating, modifying, deleting, or executing any operations. This aligns with the Read category (retrieves or queries data; no side effects).
From the tool's definition Tool description states 'Performs all container version header operations: list, latest' — purely retrieval operations with no modification, deletion, or execution of code.
Documented attack patterns abuse exactly the kind of access gtm_version_header 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_version_header:
{
"version": "1",
"default": "deny",
"tools": {
"gtm_version_header": {}
}
}gtm_version_header is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Performs all container version header operations: list, latest. The. It is categorised as a Read tool in the Google Tag Manager MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Tag Manager MCP Server MCP server in PolicyLayer and add a rule for gtm_version_header: 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_version_header is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the gtm_version_header 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_version_header. 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_version_header 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.