release_rollback
Roll a channel's latest pointer back to a previously published semver.
This record as markdown: /tools/io-github-kivanccakmak-yaver/release-rollback.md
What release_rollback does on Yaver
AI agents call release_rollback to permanently remove resources in Yaver, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
semver | string | Yes | |
channel | string | Yes |
Parameters from the server's own tool schema.
Why release_rollback is rated Critical
Rolling back a release pointer irreversibly changes the active deployment state for a channel, potentially disrupting live users and overwriting the current release pointer. This is a non-trivial operational action that cannot easily be undone without re-deploying, and misuse could cause service disruption at production scale.
From the tool's definition Roll a channel's latest pointer back to a previously published semver
Attacks that exploit this kind of access
The rule that runs release_rollback safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For release_rollback, this is the rule to start with:
release_rollback is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every release_rollback call is checked against it from then on.
Questions about release_rollback
Roll a channel's latest pointer back to a previously published semver. It is categorised as a Destructive tool in the Yaver MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
release_rollback accepts 2 parameters: semver, channel. Required: semver, channel. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for release_rollback: 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 Yaver. Nothing to install.
release_rollback is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the release_rollback 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 release_rollback. 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.
release_rollback is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
Across the catalogue