Updates an existing task (work package) in OpenProject. Only include fields to be changed.
AI agents use openproject-update-task 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 without permanently deleting or destroying records. It performs a standard update operation on a work package/task entity. While it can modify project data, the changes are not irreversible (unlike delete operations on this server) and do not involve code execution, external operations, or financial transactions.
From the tool's definition Tool name contains 'update' and description states 'Updates an existing task (work package) in OpenProject.' The description explicitly indicates it modifies data reversibly by changing only specified fields.
Documented attack patterns abuse exactly the kind of access openproject-update-task 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-update-task:
{
"version": "1",
"default": "deny",
"tools": {
"openproject-update-task": {
"limits": [
{
"counter": "openproject-update-task_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}openproject-update-task stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Updates an existing task (work package) in OpenProject. Only include fields to be changed. 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 openproject-update-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.
openproject-update-task 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 openproject-update-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.
Set action: deny in the PolicyLayer policy for openproject-update-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.
openproject-update-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.
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.