switch_rollback
Roll back a switch (git branch + env + data restore). Only valid within the 7-day TTL.
This record as markdown: /tools/io-github-kivanccakmak-yaver/switch-rollback.md
What switch_rollback does on Yaver
AI agents call switch_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 |
|---|---|---|---|
id | string | Yes | |
directory | string | — |
Parameters from the server's own tool schema.
Why switch_rollback is rated Critical
A rollback operation overwrites current state — resetting a git branch, environment configuration, and restoring data. These are irreversible overwrites of the current working state. 'Data restore' implies replacing existing data with a prior snapshot, which can cause permanent loss of changes made since the switch. The 7-day TTL constraint confirms this is a point-in-time destructive operation.
From the tool's definition Roll back a switch (git branch + env + data restore)
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs switch_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 switch_rollback, this is the rule to start with:
switch_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 switch_rollback call is checked against it from then on.
Questions about switch_rollback
Roll back a switch (git branch + env + data restore). Only valid within the 7-day TTL. 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.
switch_rollback accepts 2 parameters: id, directory. Required: id. 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 switch_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.
switch_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 switch_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 switch_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.
switch_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