AI agents use create_work_item_comment 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.
Creating comments is a Write operation—it creates new data that can be modified or deleted. It has no side effects beyond adding content to a work item. Severity is medium because while reversible, comments in project management can impact team workflows and discussions if misused. Confidence is reduced due to empty description, but the tool name clearly indicates creation of additive content.
From the tool's definition Tool name 'create_work_item_comment' indicates creation of a comment on a work item. The verb 'create' and context of Plane (a project management tool) suggest this creates reversible data. Description is empty, limiting full assessment.
Attacks that exploit this kind of access
create_work_item_comment. 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 create_work_item_comment: 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.
create_work_item_comment 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 create_work_item_comment 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 create_work_item_comment. 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.
create_work_item_comment 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 →