deep_research
AI agents invoke deep_research to trigger actions in Deep Research MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The server description indicates this tool triggers automated research pipelines using external AI providers. This constitutes executing external operations with side effects (API calls, potentially browsing, data retrieval and synthesis). The empty description lowers confidence significantly.
From the tool's definition Tool name 'deep_research' on a server described as running 'automated deep research' integrating multiple AI research providers (OpenAI, Gemini, DR-Tulu, Open Deep Research).
Attacks that exploit this kind of access
deep_research. It is categorised as a Execute tool in the Deep Research MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Deep Research MCP server in PolicyLayer and add a rule for deep_research: 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 Deep Research MCP. Nothing to install.
deep_research is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the deep_research 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_research. 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_research is provided by the Deep Research MCP server (pminervini/deep-research-mcp). 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 →