folders_move_entities
[WRITE] Move tags/triggers/variables into a folder. Requires GTM_MCP_ENABLE_WRITES=true and confirm=true.
This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/folders-move-entities.md
What folders_move_entities does on Samarth Gtm Mcp
AI agents use folders_move_entities to create or update resources in Samarth Gtm Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Samarth Gtm Mcp environment.
Why folders_move_entities is rated Medium
The tool modifies the structure and organization of GTM container elements (tags, triggers, variables) by moving them between folders. This is a write operation because it changes data state reversibly—moves can be undone by moving entities back. It requires explicit enablement (GTM_MCP_ENABLE_WRITES=true and confirm=true), indicating gated access.
From the tool's definition Tool description explicitly labels it as [WRITE] and states it 'Move tags/triggers/variables into a folder.' This is a reversible modification operation that reorganizes GTM container entities without deleting or executing code.
Attacks that exploit this kind of access
The rule that runs folders_move_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_move_entities, this is the rule to start with:
folders_move_entities stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_move_entities call is checked against it from then on.
Questions about folders_move_entities
[WRITE] Move tags/triggers/variables into a folder. Requires GTM_MCP_ENABLE_WRITES=true and confirm=true. It is categorised as a Write tool in the Samarth Gtm Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Samarth Gtm MCP server in PolicyLayer and add a rule for folders_move_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_move_entities is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the folders_move_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_move_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_move_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