folders_entities
List all entities (tags, triggers, variables) within a specific GTM folder.
This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/folders-entities.md
What folders_entities does on Samarth Gtm Mcp
AI agents call folders_entities 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 folders_entities is rated Low
This tool performs a data retrieval operation with no side effects. It lists GTM entities within a folder, which is a standard read query. The low severity reflects that unauthorized listing of GTM configuration has limited direct blast radius compared to write/execute/destructive operations. The high confidence reflects the explicit 'read-only' server design and clear query semantics.
From the tool's definition Tool name 'folders_entities' with description 'List all entities' indicates a retrieval operation. The server is explicitly described as 'read-only by default' and this tool lists (queries) tags, triggers, and variables—no modification or deletion occurs.
Attacks that exploit this kind of access
The rule that runs folders_entities 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 folders_entities, this is the rule to start with:
folders_entities 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 folders_entities call is checked against it from then on.
Questions about folders_entities
List all entities (tags, triggers, variables) within a specific GTM folder. 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 folders_entities: 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.
folders_entities 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 folders_entities 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 folders_entities. 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.
folders_entities 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