Delete a project
AI agents call delete_project to permanently remove resources in Rize — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs an irreversible deletion of a project, which cannot be undone. This falls squarely into the Destructive category per the classification rules. Severity is high because deletion of a project could impact multiple team members, associated tasks, time entries, and historical records, though it is scoped to a single resource rather than a database-wide operation (which would be critical).
From the tool's definition Tool name is 'delete_project' and description states 'Delete a project' — this is an irreversible deletion operation that destroys project data.
Attacks that exploit this kind of access
Delete a project. It is categorised as a Destructive tool in the Rize MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Rize 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 Rize. 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 Rize MCP server (rize-io/mcp-server). 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 →