Searches the web and return results in a natural language format.
AI agents call deep_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 performs a read-only query operation against web data sources and formats results for display. It has no side effects on external systems, does not execute code, does not modify data, and does not commit financial transactions. The primary risk is information sensitivity in results, which is inherent to search and does not elevate the tool's functional category beyond Read.
From the tool's definition Tool description states it 'Searches the web and return results in a natural language format.' The verb 'searches' and 'return results' indicate data retrieval with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Searches the web and return results in a natural language format. 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 deep_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.
deep_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 deep_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 deep_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.
deep_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 →