List all GTM containers in an account
AI agents call list_gtm_containers 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.
This tool performs a query/list operation to retrieve GTM container data from an account. It has no capability to modify, delete, or execute operations—it only returns information. The blast radius is minimal as it simply exposes existing container metadata that the authorized account holder can already see through the GTM UI. Classified as Read with low severity.
From the tool's definition Tool name 'list_gtm_containers' and description 'List all GTM containers in an account' indicate a retrieval operation with no modifications or side effects.
Attacks that exploit this kind of access
List all GTM containers in an account. 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 list_gtm_containers: 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.
list_gtm_containers 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 list_gtm_containers 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 list_gtm_containers. 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.
list_gtm_containers 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →