phone_project_delete
Delete a phone project (removes the SQLite file and manifest).
This record as markdown: /tools/io-github-kivanccakmak-yaver/phone-project-delete.md
What phone_project_delete does on Yaver
AI agents call phone_project_delete 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 |
|---|---|---|---|
slug | string | Yes |
Parameters from the server's own tool schema.
Why phone_project_delete is rated Critical
This tool permanently deletes project data (SQLite database and manifest file) with no stated recovery mechanism. Deletion is irreversible, making it Destructive rather than Write. The blast radius is high because an AI agent invoking this without proper safeguards could eliminate a user's entire project state.
From the tool's definition Tool name includes 'delete' and description states it 'removes the SQLite file and manifest' — both irreversible data destruction operations.
Attacks that exploit this kind of access
The rule that runs phone_project_delete 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 phone_project_delete, this is the rule to start with:
phone_project_delete 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 phone_project_delete call is checked against it from then on.
Questions about phone_project_delete
Delete a phone project (removes the SQLite file and manifest). 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.
phone_project_delete accepts 1 parameter: slug. Required: slug. 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 phone_project_delete: 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.
phone_project_delete 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 phone_project_delete 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 phone_project_delete. 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.
phone_project_delete 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