Remove a reaction from a LinkedIn post.
AI agents call linkedin_delete_reaction to permanently remove resources in Publora MVP MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a reaction is a destructive action: it deletes an existing user interaction from a LinkedIn post. While the blast radius is limited (only affects a single reaction, not critical data), it is still an irreversible deletion of a social engagement action, placing it in the Destructive category with medium severity.
From the tool's definition 'Remove a reaction from a LinkedIn post' — explicitly deletes/removes an existing reaction, which is an irreversible action (the original reaction state is lost).
Attacks that exploit this kind of access
Remove a reaction from a LinkedIn post. It is categorised as a Destructive tool in the Publora MVP MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Publora MVP MCP Server MCP server in PolicyLayer and add a rule for linkedin_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 Publora MVP MCP Server. Nothing to install.
linkedin_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 linkedin_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 linkedin_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.
linkedin_delete_reaction is provided by the Publora MVP MCP Server MCP server (paisabrazilfl-cpu/social-flow-mvp). 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 →