ops_plan
Resolve the execution plan for one ops verb without running it. Returns project context, machine placement, and caller access policy so agents can inspect deploy/reload routing and guest/share constraints ahead of time.
This record as markdown: /tools/io-github-kivanccakmak-yaver/ops-plan.md
What ops_plan does on Yaver
AI agents call ops_plan to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
verb | string | Yes | Verb name to plan for. |
machine | string | — | Target: "local", "auto", "primary", or a deviceId / alias. Same semantics as `ops`. |
payload | object | — | Verb-specific payload used for workDir / target / placement inference. |
Parameters from the server's own tool schema.
Why ops_plan is rated Low
The tool explicitly states it resolves a plan without executing it, returning read-only context about project configuration, machine placement, and access policies. No side effects are produced; it is purely an inspection/query operation.
From the tool's definition 'Resolve the execution plan...without running it' and 'so agents can inspect deploy/reload routing...ahead of time'
Risk signalsAccepts raw HTML/template content (payload)
Attacks that exploit this kind of access
The rule that runs ops_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 ops_plan, this is the rule to start with:
ops_plan is read-only, so it stays allowed. 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 ops_plan call is checked against it from then on.
Questions about ops_plan
Resolve the execution plan for one ops verb without running it. Returns project context, machine placement, and caller access policy so agents can inspect deploy/reload routing and guest/share constraints ahead of time. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
ops_plan accepts 3 parameters: verb, machine, payload. Required: verb. 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 ops_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.
ops_plan is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ops_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 ops_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.
ops_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