This record as markdown: /tools/allmcp/linear-remove-reaction.md
What linear_remove_reaction does on Allmcp
AI agents call linear_remove_reaction to permanently remove resources in Allmcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why linear_remove_reaction is rated Critical
Removing a reaction is an irreversible deletion of existing data (the reaction identified by UUID). This maps to the Destructive category. Severity is medium as the blast radius is limited to a single reaction record, which is relatively minor data.
From the tool's definition Remove a reaction by UUID
Attacks that exploit this kind of access
The rule that runs linear_remove_reaction 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_remove_reaction, this is the rule to start with:
linear_remove_reaction is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Allmcp, apply this rule, and every linear_remove_reaction call is checked against it from then on.
Questions about linear_remove_reaction
Remove a reaction by UUID. It is categorised as a Destructive tool in the Allmcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the All MCP server in PolicyLayer and add a rule for linear_remove_reaction: 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_remove_reaction is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the linear_remove_reaction 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_remove_reaction. 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_remove_reaction 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.
Across the catalogue