Delete a project. IRREVERSIBLE: requires a human to approve a native GUI dialog by retyping the project id; the agent cannot self-approve. Set MCP_HITL=off to fall back to the confirmProjectExId/force text gate in headless automation.
AI agents call delete_project to permanently remove resources in Zion — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
force | boolean | — | |
projectExId | string | Yes | |
confirmProjectExId | string | — |
Parameters from the server's own tool schema.
The tool irreversibly deletes a project, which is the definition of Destructive category. Although it includes human approval safeguards (GUI dialog or text gate), the underlying action is irreversible deletion of data. Severity is high rather than critical because the approval requirement mitigates accidental misuse, though a determined agent could still trigger it through the headless fallback.
From the tool's definition Tool name is 'delete_project' and description explicitly states 'Delete a project. IRREVERSIBLE' — this is permanent data loss without recovery.
Attacks that exploit this kind of access
Delete a project. IRREVERSIBLE: requires a human to approve a native GUI dialog by retyping the project id; the agent cannot self-approve. Set MCP_HITL=off to fall back to the confirmProjectExId/force text gate in headless automation. It is categorised as a Destructive tool in the Zion MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_project accepts 3 parameters: force, projectExId, confirmProjectExId. Required: projectExId. The full parameter table on this page comes from the server's own tool schema.
Register the Zion MCP server in PolicyLayer and add a rule for delete_project: 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 Zion. Nothing to install.
delete_project 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 delete_project 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 delete_project. 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.
delete_project is provided by the Zion MCP server (zion-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →