Search LinkedIn profiles and companies using Exa AI - finds professional profiles, company pages, and business-related content on LinkedIn. Useful for networking, recruitment, and business research.
AI agents call linkedin_search_exa to retrieve information from Exa MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries publicly or semi-publicly available LinkedIn data. It does not create, modify, delete, or execute operations—it only searches and returns information. The blast radius of misuse is limited to unwanted information gathering about individuals or companies, which is a read-level risk. No financial transactions, code execution, or data destruction is possible.
From the tool's definition Tool description states it 'Search LinkedIn profiles and companies' and is 'Useful for networking, recruitment, and business research.' The verb 'search' combined with use cases that are purely informational (finding profiles, company pages, business-related…
Attacks that exploit this kind of access
Search LinkedIn profiles and companies using Exa AI - finds professional profiles, company pages, and business-related content on LinkedIn. Useful for networking, recruitment, and business research. It is categorised as a Read tool in the Exa MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Exa MCP Server MCP server in PolicyLayer and add a rule for linkedin_search_exa: 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 Exa MCP Server. Nothing to install.
linkedin_search_exa 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 linkedin_search_exa 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_search_exa. 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_search_exa is provided by the Exa MCP Server MCP server (jordyvandomselaar/exa-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 →