machine_remove
Permanently remove Yaver from this owned host machine: unregister the device, remove auto-start service, wipe ~/.yaver, then shut the agent down. Requires confirm=true and phrase='delete my machine'.
This record as markdown: /tools/io-github-kivanccakmak-yaver/machine-remove.md
What machine_remove does on Yaver
AI agents call machine_remove 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 |
|---|---|---|---|
phrase | string | Yes | Must equal 'delete my machine' |
confirm | boolean | Yes | Must be true to confirm permanent machine removal |
Parameters from the server's own tool schema.
Why machine_remove is rated Critical
This tool irreversibly deletes configuration, unregisters devices, and terminates services on the host machine. It requires explicit confirmation (confirm=true and a deletion phrase), indicating awareness of destructive intent. The wiping of ~/.yaver and permanent removal of Yaver from the machine constitute data destruction and cannot be reversed without full reinstallation and reconfiguration.
From the tool's definition Tool description explicitly states 'Permanently remove', 'unregister the device', 'remove auto-start service', 'wipe ~/.yaver', 'shut the agent down'. These are irreversible operations that cannot be undone.
Attacks that exploit this kind of access
The rule that runs machine_remove 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 machine_remove, this is the rule to start with:
machine_remove is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every machine_remove call is checked against it from then on.
Questions about machine_remove
Permanently remove Yaver from this owned host machine: unregister the device, remove auto-start service, wipe ~/.yaver, then shut the agent down. Requires confirm=true and phrase='delete my machine'. 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.
machine_remove accepts 2 parameters: phrase, confirm. Required: phrase, confirm. 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 machine_remove: 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.
machine_remove 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 machine_remove 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 machine_remove. 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.
machine_remove 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.
Across the catalogue