Real-time web search capabilities powered by Exa AI
AI agents call web_search_exa to retrieve information from Exa Websets MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Web search retrieves and queries publicly available information. While it may make external HTTP requests to search engines, it does not execute arbitrary code, modify data, trigger financial transactions, or delete anything. The operation is read-only. Severity is low because even if misused by an agent, a web search cannot directly harm systems or data—it only gathers information.
From the tool's definition Tool description states 'Real-time web search capabilities' which retrieves data from the web without modifying, deleting, or executing code. The broader server description mentions 'perform web searches' as a core capability.
Attacks that exploit this kind of access
Real-time web search capabilities powered by Exa AI. It is categorised as a Read tool in the Exa Websets MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Exa Websets MCP Server MCP server in PolicyLayer and add a rule for web_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 Websets MCP Server. Nothing to install.
web_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 web_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 web_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.
web_search_exa is provided by the Exa Websets MCP Server MCP server (waldzellai/exa-mcp-server-websets). 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 →