AI agents call gtm_tags to retrieve information from Access without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves configuration metadata from Google Tag Manager without modifying, executing, or deleting anything. While the Access server handles sensitive credentials, this particular tool is a read-only query of GTM tag configuration.
From the tool's definition Tool 'gtm_tags' lists tags in a GTM container workspace with their type, firing triggers, and status. The description explicitly uses 'List' and 'audit' (read-only inspection) with no indication of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
List all tags configured in a GTM container workspace, including their type, firing triggers, and status. Use this to audit tracking pixels, conversion tags, or analytics configuration. It is categorised as a Read tool in the Access MCP Server, which means it retrieves data without modifying state.
Register the Access MCP server in PolicyLayer and add a rule for gtm_tags: 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 Access. Nothing to install.
gtm_tags 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_tags 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_tags. 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_tags is provided by the Access MCP server (scottpedia0/access). 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 →