Web search via DuckDuckGo HTML endpoint. Returns title + url + snippet per hit.
AI agents call search_web to retrieve information from Nexus Core without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries an external web search service and returns search results. It retrieves information without modifying, deleting, executing code, or creating side effects. The return of title, URL, and snippet metadata confirms read-only behavior typical of search operations.
From the tool's definition Tool performs 'Web search via DuckDuckGo HTML endpoint' and 'Returns title + url + snippet per hit' — purely data retrieval with no side effects.
Attacks that exploit this kind of access
Web search via DuckDuckGo HTML endpoint. Returns title + url + snippet per hit. It is categorised as a Read tool in the Nexus Core MCP Server, which means it retrieves data without modifying state.
Register the Nexus Core MCP server in PolicyLayer and add a rule for search_web: 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 Nexus Core. Nothing to install.
search_web 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 search_web 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 search_web. 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.
search_web is provided by the Nexus Core MCP server (noumenon-ai/nexus-core). 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 →