move_gtm_entities_to_folder
Move tags, triggers and/or variables into a GTM folder (organisational only, does NOT change firing). Pass at least one of tagIds / triggerIds / variableIds. To file all GA4 tags: list_gtm_tags, keep the gaawe/gaawc/googtag ids, create_gtm_folder, then call this with those tagIds.
This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/move-gtm-entities-to-folder.md
What move_gtm_entities_to_folder does on Samarth Gtm Mcp
AI agents use move_gtm_entities_to_folder 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 move_gtm_entities_to_folder is rated Medium
Reorganizes GTM entities reversibly without altering functionality or data; classic write operation with undo capability.
From the tool's definition Move tags, triggers and/or variables into a GTM folder (organisational only, does NOT change firing).
Attacks that exploit this kind of access
The rule that runs move_gtm_entities_to_folder 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 move_gtm_entities_to_folder, this is the rule to start with:
move_gtm_entities_to_folder 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 move_gtm_entities_to_folder call is checked against it from then on.
Questions about move_gtm_entities_to_folder
Move tags, triggers and/or variables into a GTM folder (organisational only, does NOT change firing). Pass at least one of tagIds / triggerIds / variableIds. To file all GA4 tags: list_gtm_tags, keep the gaawe/gaawc/googtag ids, create_gtm_folder, then call this with those tagIds. 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 move_gtm_entities_to_folder: 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.
move_gtm_entities_to_folder 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 move_gtm_entities_to_folder 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 move_gtm_entities_to_folder. 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.
move_gtm_entities_to_folder 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