AI agents use resolve_work_item_type 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 tool likely updates a work item's type attribute, which is a reversible data modification. It fits the Write category (creates or modifies data reversibly). Severity is medium because changing work item types could affect workflow routing, automation rules, and project tracking, but the change is reversible. Confidence is moderate due to the empty description and ambiguity of 'resolve' without more context.
From the tool's definition Tool name 'resolve_work_item_type' suggests modifying or setting a work item's type field. The verb 'resolve' in context of work item management typically means to set or change a property. The description is empty, which lowers precision.
Attacks that exploit this kind of access
resolve_work_item_type. 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 resolve_work_item_type: 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.
resolve_work_item_type 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 resolve_work_item_type 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 resolve_work_item_type. 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.
resolve_work_item_type 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 →