Fetch a LinkedIn profile by slug. Returns full profile data including name, headline, experience, education, and skills. Requires the OutX Chrome extension to be active within the last 48 hours. This tool handles async polling automatically.
AI agents call fetch_linkedin_profile 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.
The tool retrieves publicly available or authorized LinkedIn profile data (name, headline, experience, education, skills). This is a read operation with no side effects. Severity is medium rather than low because the data returned (full professional profiles) could enable profiling, targeting, or reconnaissance if misused at scale by an AI agent, though no irreversible harm or financial impact is possible.
From the tool's definition Tool description states 'Fetch a LinkedIn profile by slug. Returns full profile data' — purely retrieving and querying profile information with no modification, deletion, or financial impact.
Attacks that exploit this kind of access
Fetch a LinkedIn profile by slug. Returns full profile data including name, headline, experience, education, and skills. 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_profile: 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_profile 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_profile 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_profile. 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_profile 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 →