Remove a reaction from LinkedIn.
AI agents call remove_linkedin_reaction to permanently remove resources in LinkedIn MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool deletes an existing reaction from LinkedIn. While the impact is relatively limited (a reaction can be re-added), the action itself is a deletion/removal operation with no undo mechanism, placing it in the Destructive category. Severity is medium because misuse is limited to removing social reactions rather than critical data.
From the tool's definition 'Remove a reaction from LinkedIn' — removing a reaction is an irreversible deletion of a previously added reaction
Attacks that exploit this kind of access
Remove a reaction from LinkedIn. It is categorised as a Destructive tool in the LinkedIn MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the LinkedIn MCP Server MCP server in PolicyLayer and add a rule for remove_linkedin_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 MCP Server. Nothing to install.
remove_linkedin_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 remove_linkedin_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 remove_linkedin_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.
remove_linkedin_reaction is provided by the LinkedIn MCP Server MCP server (selvin-paul-raj/linkedin-mcp-server). 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 →