openproject-delete-task

THE RISK

Critical Risk

Why openproject-delete-task needs a policy

This tool permanently removes data from the OpenProject instance without the ability to recover it. While the severity is not critical (as it affects individual tasks rather than system-wide data), the irreversible nature of deletion and potential for unintended data loss if an AI agent misuses this tool with incorrect parameters justifies a 'high' severity rating.

From the tool's definition Tool description explicitly states: 'Deletes a task (work package) from OpenProject. This action is irreversible.' The verb 'Deletes' combined with 'irreversible' confirms this is a destructive operation that cannot be undone.

Documented attack patterns abuse exactly the kind of access openproject-delete-task gives an agent:

POLICY

How to control openproject-delete-task

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-task:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "openproject-delete-task"
  ]
}

openproject-delete-task disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register OpenProject MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More OpenProject MCP Server tools

Destructive openproject-delete-project Deletes a project from OpenProject. This action is irreversible. Execute start-notification-stream Starts sending periodic notifications for testing resumability Write openproject-create-project Creates a new project in OpenProject Write openproject-create-task Creates a new task (work package) in an OpenProject project Write openproject-update-project Updates an existing project in OpenProject. Only include fields to be changed. Write openproject-update-task Updates an existing task (work package) in OpenProject. Only include fields to be changed. Read openproject-get-project Gets a specific project by its ID from OpenProject Read openproject-get-task Gets a specific task (work package) by its ID from OpenProject

All 11 OpenProject MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in OpenProject MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about openproject-delete-task

What does the openproject-delete-task tool do? +

Deletes a task (work package) 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.

How do I enforce a policy on openproject-delete-task? +

Register the OpenProject MCP Server MCP server in PolicyLayer and add a rule for openproject-delete-task: 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.

What risk level is openproject-delete-task? +

openproject-delete-task is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit openproject-delete-task? +

Yes. Add a rate_limit block to the openproject-delete-task 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.

How do I block openproject-delete-task completely? +

Set action: deny in the PolicyLayer policy for openproject-delete-task. 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.

What MCP server provides openproject-delete-task? +

openproject-delete-task 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.

Enforce policy on every OpenProject MCP Server tool call.

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.

CHECK YOUR STACK →