Search LinkedIn for companies using Exa AI. Simply include company URL, or company name, with 'company page' appended in your query.
Accepts freeform code/query input (query)
Part of the Exa AI Search Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call linkedin_search to retrieve information from Exa AI Search Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though linkedin_search only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
linkedin_search:
rules:
- action: allowSee the full Exa AI Search Server policy for all 8 tools.
Agents calling read-class tools like linkedin_search have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Search LinkedIn for companies using Exa AI. Simply include company URL, or company name, with 'company page' appended in your query.. It is categorised as a Read tool in the Exa AI Search Server MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for linkedin_search. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Exa AI Search Server MCP server.
linkedin_search 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 rule in your Intercept 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 Intercept policy for linkedin_search. 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 is provided by the Exa AI Search Server MCP server (jackedelic/exa-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.