This record as markdown: /tools/io-github-kivanccakmak-yaver/cloud-destroy.md
What cloud_destroy does on Yaver
AI agents call cloud_destroy 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 |
|---|---|---|---|
confirm | boolean | — | Must be true to proceed |
Parameters from the server's own tool schema.
Why cloud_destroy is rated Critical
Destroys cloud infrastructure; cannot be undone without restoration from backups.
From the tool's definition Tear down Yaver Cloud deployment; irreversibly removes infrastructure and services.
Attacks that exploit this kind of access
The rule that runs cloud_destroy 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 cloud_destroy, this is the rule to start with:
cloud_destroy 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 cloud_destroy call is checked against it from then on.
Questions about cloud_destroy
Tear down Yaver Cloud deployment (exports data first). 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.
cloud_destroy accepts 1 parameter: 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 cloud_destroy: 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.
cloud_destroy 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 cloud_destroy 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 cloud_destroy. 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.
cloud_destroy 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