copy_workspace_resources
COPY all tags, triggers and variables from one workspace into another in the SAME container. GTM has no atomic move, so this RECREATES them, remapping firing/blocking trigger references, built-in trigger ids and trigger-group members. Non-destructive: a resource whose NAME already exists in the d...
This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/copy-workspace-resources.md
What copy_workspace_resources does on Samarth Gtm Mcp
AI agents use copy_workspace_resources 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 copy_workspace_resources is rated Medium
Creates and modifies GTM resources (tags, triggers, variables) across workspaces with reference remapping, causing configuration changes that affect tracking behavior.
From the tool's definition COPY all tags, triggers and variables from one workspace into another. RECREATES them, remapping references.
Attacks that exploit this kind of access
The rule that runs copy_workspace_resources 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 copy_workspace_resources, this is the rule to start with:
copy_workspace_resources 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 copy_workspace_resources call is checked against it from then on.
Questions about copy_workspace_resources
COPY all tags, triggers and variables from one workspace into another in the SAME container. GTM has no atomic move, so this RECREATES them, remapping firing/blocking trigger references, built-in trigger ids and trigger-group members. Non-destructive: a resource whose NAME already exists in the destination is SKIPPED, never overwritten. Variable {{references}} carry over by name. NOT copied: folders, built-in variables, clients/transformations, and tags using legacy firing/blocking RULES, all listed in. 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 copy_workspace_resources: 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.
copy_workspace_resources 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 copy_workspace_resources 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 copy_workspace_resources. 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.
copy_workspace_resources 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