switch_run

Execute a previously-planned switch. HARD switches emit a rewrite prompt for the AI agent instead of running inline.

SERVERYaver SOURCEyaver-cli

High RISK CLASS

Category Execute

Parameters 21 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/switch-run.md

WHAT IT DOES

What switch_run does on Yaver

AI agents invoke switch_run to trigger actions in Yaver. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`id`	string	Yes
`directory`	string	—

Parameters from the server's own tool schema.

RISK

Why switch_run is rated High

The tool executes a planned operation (a 'switch'), which implies triggering an external action or code transformation. The 'HARD switch' path emits a rewrite prompt to the AI agent, meaning it can cause the agent to rewrite code or configuration. This is an Execute-category action with high severity because misuse could trigger unintended code rewrites or deployments in a development environment.

From the tool's definition "Execute a previously-planned switch" and "emit a rewrite prompt for the AI agent instead of running inline"

Risk signalsAccepts file system path (directory)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs switch_run 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_run, this is the rule to start with:

switch_run Rate-limited

switch_run stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "switch_run": {
      "limits": [
        {
          "counter": "switch_run_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every switch_run call is checked against it from then on.

FAQ

Questions about switch_run

What does the switch_run tool do? +

Execute a previously-planned switch. HARD switches emit a rewrite prompt for the AI agent instead of running inline. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does switch_run accept? +

switch_run accepts 2 parameters: id, directory. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on switch_run? +

Register the Yaver MCP server in PolicyLayer and add a rule for switch_run: 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.

What risk level is switch_run? +

switch_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit switch_run? +

Yes. Add a rate_limit block to the switch_run 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.

How do I block switch_run completely? +

Set action: deny in the PolicyLayer policy for switch_run. 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.

What MCP server provides switch_run? +

switch_run 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.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools → High-risk tools on this server →

Across the catalogue

shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →