Check the status and retrieve results of a deep research task. This tool monitors the progress of an AI agent that performs comprehensive web searches, analyzes multiple sources, and synthesizes findings into detailed research reports. The tool includes a built-in 5-second delay before checking t...
AI agents call deep_researcher_check 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 status checking and result retrieval from a previously initiated deep research task. It queries state without modifying it, making it a Read operation. The 5-second polling delay is a client-side implementation detail, not a side effect. Severity is low because retrieving research results poses minimal risk—the agent cannot alter data, execute commands, or cause harm through this tool alone.
From the tool's definition Tool description states it 'Check[s] the status and retrieve[s] results' and 'monitors the progress' of research tasks. The verb 'retrieve' and 'check' indicate data retrieval with no modification or side effects. The tool 'polls' for status—a read operation.
Attacks that exploit this kind of access
Check the status and retrieve results of a deep research task. This tool monitors the progress of an AI agent that performs comprehensive web searches, analyzes multiple sources, and synthesizes findings into detailed research reports. The tool includes a built-in 5-second delay before checking to allow processing time. IMPORTANT: You must call this tool repeatedly (poll) until the status becomes. 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_researcher_check: 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_researcher_check 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_researcher_check 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_researcher_check. 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_researcher_check 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 →