versions_publish
[PUBLISH] Publish a specific GTM container version to live.
This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/versions-publish.md
What versions_publish does on Samarth Gtm Mcp
AI agents invoke versions_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 versions_publish is rated High
Publishing a GTM container version to live is an external operation with immediate, broad impact: it affects all users of the website/app instrumented by that container. While it is technically reversible (you can republish a prior version), the act of publishing itself is an Execute-class action that triggers a significant external state change.
From the tool's definition '[PUBLISH] Publish a specific GTM container version to live.' — triggers an external operation that pushes a GTM container version to the live production environment.
Attacks that exploit this kind of access
The rule that runs versions_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 versions_publish, this is the rule to start with:
versions_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 versions_publish call is checked against it from then on.
Questions about versions_publish
[PUBLISH] Publish a specific GTM container version to live. 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 versions_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.
versions_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 versions_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 versions_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.
versions_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