versions_set_latest
[WRITE] Set a specific container version as the
This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/versions-set-latest.md
What versions_set_latest does on Samarth Gtm Mcp
AI agents use versions_set_latest 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 versions_set_latest is rated Medium
This tool modifies GTM container state by selecting which version is active/latest. This is a reversible change (a different version can be set later) that does not delete data or execute arbitrary code. It fits Write category. Severity is medium because misconfiguration could break tracking or analytics, but the operation is gated, audited (per server description), and reversible.
From the tool's definition Tool name prefix '[WRITE]' and verb 'set' indicate modification. Description states 'Set a specific container version as the' (truncated but clearly a state-changing operation). Container version selection affects GTM behavior and tracking configuration.
Attacks that exploit this kind of access
The rule that runs versions_set_latest 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_set_latest, this is the rule to start with:
versions_set_latest 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 versions_set_latest call is checked against it from then on.
Questions about versions_set_latest
[WRITE] Set a specific container version as the. 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 versions_set_latest: 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_set_latest 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 versions_set_latest 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_set_latest. 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_set_latest 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