containers_move_tag_id
[WRITE] Move a Tag ID out of a container into a new container.
This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/containers-move-tag-id.md
What containers_move_tag_id does on Samarth Gtm Mcp
AI agents use containers_move_tag_id 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 containers_move_tag_id is rated Medium
This tool creates or modifies GTM container configuration by relocating tags between containers. While reversible (tags can be moved back), it alters production tracking infrastructure and could disrupt data collection if misused. The high severity reflects potential impact on analytics pipelines and tag execution.
From the tool's definition Tool description explicitly marked [WRITE] and performs 'Move a Tag ID out of a container into a new container' — a reversible modification of GTM container structure and tag organization.
Attacks that exploit this kind of access
The rule that runs containers_move_tag_id 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_move_tag_id, this is the rule to start with:
containers_move_tag_id 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 containers_move_tag_id call is checked against it from then on.
Questions about containers_move_tag_id
[WRITE] Move a Tag ID out of a container into a new container. 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 containers_move_tag_id: 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_move_tag_id 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 containers_move_tag_id 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_move_tag_id. 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_move_tag_id 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