switch_plan
Plan a backend/host switch. Assesses complexity (trivial/easy/medium/hard) and generates ordered steps across 7 layers (data/code/env/infra/network/integrations/verify). Persists the plan — use switch_run to execute.
This record as markdown: /tools/io-github-kivanccakmak-yaver/switch-plan.md
What switch_plan does on Yaver
AI agents use switch_plan to create or update resources in Yaver, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
dryRun | boolean | — | |
target | string | Yes | |
directory | string | — |
Parameters from the server's own tool schema.
Why switch_plan is rated Medium
The tool generates and persists a migration plan across 7 layers (data/code/env/infra/network/integrations/verify) but does not execute it. Execution is deferred to a separate 'switch_run' tool. Persisting a plan is a Write operation (creates/stores data reversibly), not Destructive or Execute since no infrastructure changes are applied yet.
From the tool's definition Persists the plan — use switch_run to execute
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs switch_plan 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_plan, this is the rule to start with:
switch_plan 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 Yaver, apply this rule, and every switch_plan call is checked against it from then on.
Questions about switch_plan
Plan a backend/host switch. Assesses complexity (trivial/easy/medium/hard) and generates ordered steps across 7 layers (data/code/env/infra/network/integrations/verify). Persists the plan — use switch_run to execute. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
switch_plan accepts 3 parameters: dryRun, target, directory. Required: target. 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_plan: 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_plan 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 switch_plan 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_plan. 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_plan 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.
This server
Across the catalogue