AI agents call delete_reaction to permanently remove resources in LinkedIn Intelligence MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Although reactions themselves are minor engagement artifacts, deletion operations are categorized as Destructive because they irreversibly remove data. The moderate severity reflects that individual reactions have limited blast radius compared to bulk content deletion, but the irreversible nature of deletion justifies the Destructive category over Write.
From the tool's definition Tool name 'delete_reaction' indicates irreversible removal of a reaction entity. The description is empty, but the naming convention combined with the server's focus on LinkedIn engagement automation strongly suggests this tool deletes user reaction data that…
Documented attack patterns abuse exactly the kind of access delete_reaction gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LinkedIn Intelligence MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_reaction:
{
"version": "1",
"default": "deny",
"hide": [
"delete_reaction"
]
}delete_reaction disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
delete_reaction. It is categorised as a Destructive tool in the LinkedIn Intelligence MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the LinkedIn Intelligence MCP Server MCP server in PolicyLayer and add a rule for delete_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 LinkedIn Intelligence MCP Server. Nothing to install.
delete_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 delete_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 delete_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.
delete_reaction is provided by the LinkedIn Intelligence MCP Server MCP server (southleft/linkedin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 87 LinkedIn Intelligence MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
87 LinkedIn Intelligence MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.