AI agents use create_comment to create or update resources in Linear — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Linear environment.
This tool creates new data (a comment) in a Linear workspace, which is a write operation. The action is reversible (comments can be deleted), so it does not qualify as Destructive. There are no financial implications. Severity is low because the blast radius of an accidentally created comment is minimal—it can be easily removed and causes no data loss or system compromise.
From the tool's definition Tool description: "Create a new comment in Linear". The verb "create" and the sibling tools include destructive operations (delete_comment, delete_issue), which confirms this server supports CRUD operations. Creating a comment is a reversible modification.
Attacks that exploit this kind of access
Create a new comment in Linear. It is categorised as a Write tool in the Linear MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Linear MCP server in PolicyLayer and add a rule for create_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 Linear. Nothing to install.
create_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_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_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_comment is provided by the Linear MCP server (mkusaka/mcp-server-linear). 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 →