Run one verb on one machine. Single API for every Yaver capability (info, run, build, test, deploy, push, reload, logs, status, env, session, scale, provision, destroy, ...). Discover available verbs via ops_verbs.
AI agents call ops 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 |
|---|---|---|---|
verb | string | Yes | Verb name. Call ops_verbs for the registered list + each verb's payload schema. |
machine | string | — | Target: "local", "auto", "primary", or a deviceId / alias. Cross-machine routing is supported; "auto" uses project-aware placement for deploy/reload and otherwi |
payload | object | — | Verb-specific payload. Shape depends on verb. |
Parameters from the server's own tool schema.
An AI agent that decides to call ops doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Yaver is gone — there is no undo for destructive operations.
Risk signalsAccepts raw HTML/template content (payload) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Run one verb on one machine. Single API for every Yaver capability (info, run, build, test, deploy, push, reload, logs, status, env, session, scale, provision, destroy, ...). Discover available verbs via ops_verbs. 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.
ops 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: 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 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 ops 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. 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 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.