AI agents call delete_project to permanently remove resources in Zoho Projects MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of a project is an irreversible destructive action that cannot be undone by normal means (though it moves to trash rather than permanent deletion, it is still outside user recovery scope for practical purposes). The blast radius is high because a single misuse could eliminate an entire project and its associated tasks, issues, and milestones. This is the most severe category applicable.
From the tool's definition Tool name is 'delete_project' and description states 'Delete a project (moves to trash)' — this irreversibly removes a project from active use, preventing further work on it and destroying associated data relationships.
Documented attack patterns abuse exactly the kind of access delete_project gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Zoho Projects MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_project:
{
"version": "1",
"default": "deny",
"hide": [
"delete_project"
]
}delete_project disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a project (moves to trash). It is categorised as a Destructive tool in the Zoho Projects MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Zoho Projects MCP Server 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 Zoho Projects MCP Server. 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 Zoho Projects MCP Server MCP server (qpiai/zoho-projects-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Zoho Projects MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
20 Zoho Projects MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.