AI agents use plane-work-item-comment-add 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.
Adding comments is a Write operation—it creates new data (a comment record) but does not execute arbitrary code, delete data, or cause financial effects. The action is reversible (comments can typically be edited or deleted). The blast radius is low since comments are user-generated content with limited downstream impact. Confidence is high due to the clear and descriptive tool name and functional description.
From the tool's definition The tool 'plane-work-item-comment-add' explicitly adds a comment to a work item, which is a reversible data creation/modification operation.
Attacks that exploit this kind of access
Add a comment to a work item. Accepts markdown (default) or HTML. 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 plane-work-item-comment-add: 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.
plane-work-item-comment-add 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 plane-work-item-comment-add 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 plane-work-item-comment-add. 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.
plane-work-item-comment-add is provided by the Plane MCP server (philipvanlewis/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 →