Remove the parent relationship from a work package
AI agents use remove_work_package_parent to create or update resources in OpenProject MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OpenProject MCP Server environment.
This tool modifies the relationship structure of a work package by removing its parent association. It is a reversible write operation (the parent can be reassigned), not a deletion of the work package itself. The blast radius is medium as it affects project hierarchy and task organization but does not destroy data.
From the tool's definition Remove the parent relationship from a work package
Attacks that exploit this kind of access
Remove the parent relationship from a work package. It is categorised as a Write tool in the OpenProject MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the OpenProject MCP Server MCP server in PolicyLayer and add a rule for remove_work_package_parent: 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.
remove_work_package_parent is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the remove_work_package_parent 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 remove_work_package_parent. 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.
remove_work_package_parent is provided by the OpenProject MCP Server MCP server (widjis/mcp-openproject). 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 →