AI agents use linear_add_attachment to create or update resources in Linearapp — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Linearapp environment.
This tool modifies an existing issue by adding an attachment to it. This is a reversible write operation—attachments can typically be removed or replaced. It does not retrieve data (Read), execute arbitrary code (Execute), permanently delete data (Destructive), or move money (Financial).
From the tool's definition Tool name 'linear_add_attachment' and description 'Add an attachment to an issue in Linear' indicate creation/modification of issue data by attaching files.
Attacks that exploit this kind of access
Add an attachment to an issue in Linear. It is categorised as a Write tool in the Linearapp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Linearapp MCP server in PolicyLayer and add a rule for linear_add_attachment: 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 Linearapp. Nothing to install.
linear_add_attachment 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_attachment 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_attachment. 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_attachment is provided by the Linearapp MCP server (mcp-server-linearapp). 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 →