Add a comment to a Linear issue.
AI agents use linear_add_comment to create or update resources in Integrations MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Integrations MCP environment.
Adding a comment creates new data in Linear but does not delete, destroy, or irreversibly alter existing data. It is reversible (comments can be edited or deleted). This is a Write operation. Severity is medium because an agent could spam comments, vandalize issues, or post sensitive information to collaborative project management systems, affecting team workflows and data integrity.
From the tool's definition Tool name 'linear_add_comment' and description 'Add a comment to a Linear issue' indicate creation of new content (a comment) within Linear, which is a reversible modification.
Attacks that exploit this kind of access
Add a comment to a Linear issue. It is categorised as a Write tool in the Integrations MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Integrations MCP server in PolicyLayer and add a rule for linear_add_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 Integrations MCP. Nothing to install.
linear_add_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 linear_add_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 linear_add_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.
linear_add_comment is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). 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 →