AI agents call deep_search to retrieve information from Proxima without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name strongly suggests a search operation (Read category). The server's purpose is querying multiple AI providers and data sources. Sibling tools cluster around retrieval and analysis without modification. However, lack of a description creates uncertainty about whether it might execute queries with side effects or perform API calls that trigger external state changes.
From the tool's definition Tool name 'deep_search' indicates information retrieval; sibling tools like 'academic_search', 'analyze_document', and 'ask_*' are all Read operations. No description provided to confirm, lowering confidence.
Documented attack patterns abuse exactly the kind of access deep_search gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Proxima, and nothing reaches the server without passing your rules. This is the rule we recommend for deep_search:
{
"version": "1",
"default": "deny",
"tools": {
"deep_search": {}
}
}deep_search is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
deep_search. It is categorised as a Read tool in the Proxima MCP Server, which means it retrieves data without modifying state.
Register the Proxima MCP server in PolicyLayer and add a rule for deep_search: 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 Proxima. Nothing to install.
deep_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 deep_search 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. 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 is provided by the Proxima MCP server (zen4-bit/proxima). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 50 Proxima tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
50 Proxima tools catalogued and risk-classified — across an index of 42,500+ MCP servers.