containers_lookup
Look up a GTM container by its linked destination ID (e.g. a GA4 measurement ID or tag ID).
This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/containers-lookup.md
What containers_lookup does on Samarth Gtm Mcp
AI agents call containers_lookup to retrieve information from Samarth Gtm Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why containers_lookup is rated Low
This tool retrieves metadata about GTM containers based on a lookup parameter. It performs a search/query operation with no side effects, which is characteristic of the Read category. The low severity reflects that container metadata retrieval poses minimal risk even if misused by an AI agent, as it merely returns existing configuration data without enabling changes or code execution.
From the tool's definition Tool description states 'Look up a GTM container' — a retrieval operation with no modification. The function name 'containers_lookup' and the server context ('read-only by default') both indicate query-only functionality.
Attacks that exploit this kind of access
The rule that runs containers_lookup safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Samarth Gtm Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For containers_lookup, this is the rule to start with:
containers_lookup is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Samarth Gtm Mcp, apply this rule, and every containers_lookup call is checked against it from then on.
Questions about containers_lookup
Look up a GTM container by its linked destination ID (e.g. a GA4 measurement ID or tag ID). It is categorised as a Read tool in the Samarth Gtm Mcp MCP Server, which means it retrieves data without modifying state.
Register the Samarth Gtm MCP server in PolicyLayer and add a rule for containers_lookup: 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 Samarth Gtm Mcp. Nothing to install.
containers_lookup 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 containers_lookup 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 containers_lookup. 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.
containers_lookup is provided by the Samarth Gtm MCP server (samarth-gtm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Samarth Gtm, and thousands of servers like it.
This server
Across the catalogue