Deletes a project from OpenProject. This action is irreversible.
AI agents call openproject-delete-project to permanently remove resources in OpenProject MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible deletion of an entire project, which destroys all associated data and cannot be undone. This is a clear Destructive category action. Severity is high because deleting a project could impact multiple users, workflows, and associated work packages within OpenProject, though the blast radius is scoped to that project.
From the tool's definition Tool description explicitly states: 'Deletes a project from OpenProject. This action is irreversible.' The tool name 'openproject-delete-project' and the irreversible nature of the operation directly indicate a destructive action.
Documented attack patterns abuse exactly the kind of access openproject-delete-project gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OpenProject MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for openproject-delete-project:
{
"version": "1",
"default": "deny",
"hide": [
"openproject-delete-project"
]
} openproject-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.
Deletes a project from OpenProject. This action is irreversible. It is categorised as a Destructive tool in the OpenProject MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the OpenProject MCP Server MCP server in PolicyLayer and add a rule for openproject-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 OpenProject MCP Server. Nothing to install.
openproject-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 openproject-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 openproject-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.
openproject-delete-project is provided by the OpenProject MCP Server MCP server (jessebautista/mcp-openproject-smithery). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OpenProject 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.
11 OpenProject MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.