AI agents invoke like_linkedin_post to trigger actions in Outx. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool performs a real, externally visible social action on LinkedIn (liking a post). It is not merely reading data or writing local data — it executes an interaction with an external platform. Misuse could result in unwanted social engagement at scale, reputational harm, or policy violations, hence high severity.
From the tool's definition 'Like a LinkedIn post by its activity URN (direct LinkedIn action)' — triggers an external operation on LinkedIn on behalf of the user
Attacks that exploit this kind of access
Like a LinkedIn post by its activity URN (direct LinkedIn action). Use this when you have a. It is categorised as a Execute tool in the Outx MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Outx MCP server in PolicyLayer and add a rule for like_linkedin_post: 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 Outx. Nothing to install.
like_linkedin_post is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the like_linkedin_post 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 like_linkedin_post. 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.
like_linkedin_post is provided by the Outx MCP server (outx-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 →