switch_runner
Switch the active AI runner. Available: claude, codex, aider.
This record as markdown: /tools/io-github-kivanccakmak-yaver/switch-runner.md
What switch_runner does on Yaver
AI agents use switch_runner 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 |
|---|---|---|---|
runner_id | string | Yes | Runner ID — claude, codex, or opencode. |
Parameters from the server's own tool schema.
Why switch_runner is rated Medium
This tool modifies the active configuration/state of the system by switching which AI runner is active. It is reversible (you can switch back), so it falls under Write rather than Destructive. Misuse could disrupt ongoing operations by switching runners unexpectedly, giving it medium severity.
From the tool's definition Switch the active AI runner. Available: claude, codex, aider.
Attacks that exploit this kind of access
The rule that runs switch_runner 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_runner, this is the rule to start with:
switch_runner 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_runner call is checked against it from then on.
Questions about switch_runner
Switch the active AI runner. Available: claude, codex, aider. 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_runner accepts 1 parameter: runner_id. Required: runner_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_runner: 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_runner 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_runner 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_runner. 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_runner 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