Update an existing work package
AI agents use update_work_package 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 creates or modifies data reversibly by updating an existing work package. Updates are reversible (can be overwritten or reverted), so it does not qualify as Destructive. It does not execute arbitrary code or trigger external operations based on variable arguments, so it is not Execute.
From the tool's definition Tool name 'update_work_package' and description 'Update an existing work package' indicate modification of existing data without deletion or irreversible changes.
Attacks that exploit this kind of access
Update an existing 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 update_work_package: 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.
update_work_package 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 update_work_package 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 update_work_package. 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.
update_work_package 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 →