Fetch recent posts from a LinkedIn company page by slug. Returns posts with engagement data (likes, comments, shares). Requires the OutX Chrome extension to be active within the last 48 hours. This tool handles async polling automatically.
AI agents call fetch_linkedin_company_posts to retrieve information from Outx without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves publicly available LinkedIn company post data and engagement metrics. It has no side effects, does not modify or delete data, and does not execute external operations. The requirement for the OutX Chrome extension does not elevate the risk category, as it is merely an authentication/access mechanism.
From the tool's definition Tool description states it 'Fetch[es] recent posts from a LinkedIn company page' and 'Returns posts with engagement data' — purely retrieval operations with no modification, deletion, or execution of commands.
Attacks that exploit this kind of access
Fetch recent posts from a LinkedIn company page by slug. Returns posts with engagement data (likes, comments, shares). Requires the OutX Chrome extension to be active within the last 48 hours. This tool handles async polling automatically. It is categorised as a Read tool in the Outx MCP Server, which means it retrieves data without modifying state.
Register the Outx MCP server in PolicyLayer and add a rule for fetch_linkedin_company_posts: 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.
fetch_linkedin_company_posts is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the fetch_linkedin_company_posts 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 fetch_linkedin_company_posts. 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.
fetch_linkedin_company_posts 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 →