AI agents call ddg_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.
This tool performs a search query and returns structured metadata results. It has no side effects, does not modify any state, does not execute code, and does not access sensitive data beyond what a public web search would reveal. It is a straightforward Read operation with minimal security risk.
From the tool's definition Tool description explicitly states it "returning ranked title/URL/snippet results" and instructs users to "use web_scrape to read one" for actual content retrieval.
Attacks that exploit this kind of access
Free web search via DuckDuckGo returning ranked title/URL/snippet results (no API key). Use to find pages; use web_scrape to read one, or deep_search for AI-synthesized research. 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 ddg_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.
ddg_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 ddg_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 ddg_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.
ddg_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.
ddg_search is one line of Proxima's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →