linear_update_attachment
A write tool on the All MCP server.
This record as markdown: /tools/allmcp/linear-update-attachment.md
What linear_update_attachment does on Allmcp
AI agents use linear_update_attachment to create or update resources in Allmcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Allmcp environment.
Why linear_update_attachment is rated Medium
The tool performs an update operation on an attachment, which is a Write action. Since the description is empty, confidence is reduced. Severity is medium rather than high because attachment updates typically have limited blast radius compared to core data modifications, though the actual impact depends on what attachments contain and how they're used in the Linear integration.
From the tool's definition Tool name 'linear_update_attachment' indicates modification of an attachment resource via the 'update' verb, suggesting reversible data change.
Attacks that exploit this kind of access
The rule that runs linear_update_attachment safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Allmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For linear_update_attachment, this is the rule to start with:
linear_update_attachment stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Allmcp, apply this rule, and every linear_update_attachment call is checked against it from then on.
Questions about linear_update_attachment
linear_update_attachment is a write tool on the All MCP server. It is categorised as a Write tool in the Allmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the All MCP server in PolicyLayer and add a rule for linear_update_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 Allmcp. Nothing to install.
linear_update_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_update_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_update_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_update_attachment is provided by the All MCP server (Perception-Dynamics-Inc/allmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on All, and thousands of servers like it.
This server
Across the catalogue