Get GTM configurations with optional filtering
AI agents call get_gtm_configs 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 retrieves GTM configurations without modifying or deleting them, placing it in the Read category. Severity is medium rather than low because GTM configurations typically contain sensitive information such as tracking IDs, pixel codes, API keys, and business logic that could be misused if an AI agent exfiltrates this data to unauthorized parties or uses it to understand site infrastructure for attacks.
From the tool's definition Tool name 'get_gtm_configs' and description 'Get GTM configurations' indicate a retrieval operation with no modification.
Attacks that exploit this kind of access
Get GTM configurations with optional filtering. 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 get_gtm_configs: 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.
get_gtm_configs 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 get_gtm_configs 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 get_gtm_configs. 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.
get_gtm_configs 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 →