list_gtm_containers
List the GTM containers within a GTM account. Requires the numeric accountId.
This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/list-gtm-containers.md
What list_gtm_containers does on Samarth Gtm Mcp
AI agents call list_gtm_containers 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 list_gtm_containers is rated Low
This tool queries and returns a list of existing GTM containers associated with an account. It has no side effects, cannot modify data, and represents a straightforward informational retrieval. The blast radius of misuse is minimal—an attacker gains visibility into container configuration but cannot alter or execute changes.
From the tool's definition Tool description states 'List the GTM containers' which is a retrieval operation. The server description emphasizes 'read-only by default' and this sibling tool is grouped among other read and audit operations (accounts_list, audit_* tools).
Attacks that exploit this kind of access
The rule that runs list_gtm_containers 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 list_gtm_containers, this is the rule to start with:
list_gtm_containers 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 list_gtm_containers call is checked against it from then on.
Questions about list_gtm_containers
List the GTM containers within a GTM account. Requires the numeric accountId. 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 list_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 Samarth Gtm Mcp. Nothing to install.
list_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 list_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 list_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.
list_gtm_containers 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