workspace_create_version_and_publish
[PUBLISH] Create a new container version from a workspace and immediately publish it.
This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/workspace-create-version-and-publish.md
What workspace_create_version_and_publish does on Samarth Gtm Mcp
AI agents invoke workspace_create_version_and_publish to trigger actions in Samarth Gtm Mcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why workspace_create_version_and_publish is rated High
This tool creates a GTM container version and immediately publishes it to production. Publishing a container version triggers external operations that affect live website/app tracking for all visitors — changes propagate instantly and globally. While a prior version could theoretically be restored, the act of publishing is an external, immediately-effective operation with significant blast radius.
From the tool's definition [PUBLISH] Create a new container version from a workspace and immediately publish it.
Attacks that exploit this kind of access
The rule that runs workspace_create_version_and_publish 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 workspace_create_version_and_publish, this is the rule to start with:
workspace_create_version_and_publish stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 workspace_create_version_and_publish call is checked against it from then on.
Questions about workspace_create_version_and_publish
[PUBLISH] Create a new container version from a workspace and immediately publish it. It is categorised as a Execute tool in the Samarth Gtm Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Samarth Gtm MCP server in PolicyLayer and add a rule for workspace_create_version_and_publish: 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.
workspace_create_version_and_publish is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the workspace_create_version_and_publish 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 workspace_create_version_and_publish. 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.
workspace_create_version_and_publish 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.
Across the catalogue