AI agents use manage_work_item_assignee 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.
This tool modifies work item data by changing assignee assignments, which is a reversible operation typical of Write category. It affects project management workflows but lacks the irreversibility of Destructive actions. Severity is medium because assigning/unassigning work items could disrupt task allocation or project timelines if misused by an AI agent, but effects are reversible through reassignment.
From the tool's definition Tool name 'manage_work_item_assignee' indicates modification of work item properties (assignee field). The verb 'manage' in context of an assignee field implies create, update, or remove operations. Description is empty, which reduces confidence.
Attacks that exploit this kind of access
manage_work_item_assignee. 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 manage_work_item_assignee: 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.
manage_work_item_assignee 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 manage_work_item_assignee 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 manage_work_item_assignee. 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.
manage_work_item_assignee 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 →