Get detailed GTM configuration by ID
AI agents call get_gtm_config_details 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 and queries GTM configuration details without side effects. It is a straightforward data retrieval operation that does not create, modify, delete, or execute any actions.
From the tool's definition Tool name is 'get_gtm_config_details' and description states 'Get detailed GTM configuration by ID'. The verb 'Get' and retrieval-oriented language indicate a read-only query operation that retrieves existing configuration data without modification.
Attacks that exploit this kind of access
Get detailed GTM configuration by ID. 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_config_details: 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_config_details 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_config_details 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_config_details. 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_config_details 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 →