AI agents call gtm_containers 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 and lists existing GTM (Google Tag Manager) container information without creating, modifying, deleting, or executing any operations. It is purely informational in nature. The server context indicates this is a credential proxy with per-agent permissioning, so exposure is somewhat mitigated, but the tool itself performs no destructive actions.
From the tool's definition Tool name 'gtm_containers' and description 'List all GTM containers' indicate a retrieval/query operation with no side effects. Returns read-only metadata (container IDs, names, website URLs).
Attacks that exploit this kind of access
List all GTM containers within a specific Tag Manager account. Returns container IDs, names, and website URLs. Use after gtm_accounts to drill down. 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_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 Access. Nothing to install.
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 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 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.
gtm_containers 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 →