AI agents use update_work_item to create or update resources in Plane — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Plane environment.
The 'update_work_item' tool modifies work item data within a project management system. This is a Write operation because it creates or modifies data reversibly—updates can be undone through subsequent updates or rollbacks. It does not delete data (Destructive), does not move money (Financial), does not execute arbitrary code (Execute), and does not merely retrieve data (Read).
From the tool's definition Tool name 'update_work_item' indicates modification of existing work item data. The sibling tools on this server include create_cycle, create_initiative, create_intake_work_item, create_label, create_milestone, create_module, create_page, which are all Write…
Attacks that exploit this kind of access
update_work_item. It is categorised as a Write tool in the Plane MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Plane MCP server in PolicyLayer and add a rule for update_work_item: 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 Plane. Nothing to install.
update_work_item 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_item 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_item. 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_item is provided by the Plane MCP server (@makeplane/plane-mcp-server). 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 →