React to a LinkedIn post (like, praise, etc.)
AI agents use linkedin_create_reaction to create or update resources in Publora MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Publora MCP Server environment.
This tool creates or adds a reaction to an existing post—a reversible, non-destructive modification. It does not retrieve data (Read), execute arbitrary code (Execute), delete anything (Destructive), or move money (Financial). The severity is medium because unintended reactions could spam accounts or create reputational issues, but the action is easily undone by deletion.
From the tool's definition Tool name 'linkedin_create_reaction' and description 'React to a LinkedIn post (like, praise, etc.)' indicate creation of a reaction entity on LinkedIn.
Attacks that exploit this kind of access
React to a LinkedIn post (like, praise, etc.). It is categorised as a Write tool in the Publora MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Publora MCP Server MCP server in PolicyLayer and add a rule for linkedin_create_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 MCP Server. Nothing to install.
linkedin_create_reaction 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 linkedin_create_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_create_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_create_reaction is provided by the Publora MCP Server MCP server (publora/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 →