nodebench.search_public_sources
Search NodeBench public research memory and source cache for public facts about an entity. Private email, resume, and inbox text must not be sent here.
This record as markdown: /tools/io-github-homenshum-nodebench/nodebench.search-public-sources.md
What nodebench.search_public_sources does on Nodebench
AI agents call nodebench.search_public_sources to retrieve information from Nodebench without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why nodebench.search_public_sources is rated Low
This tool performs information retrieval only—it queries existing data without creating, modifying, deleting, or executing anything. The explicit restriction against sending private data confirms its read-only intent. The low severity reflects minimal blast radius if misused by an AI agent, as it only returns pre-existing public information.
From the tool's definition Tool name contains 'search' and description explicitly states it retrieves 'public facts' from a 'public research memory and source cache' with no mention of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs nodebench.search_public_sources safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For nodebench.search_public_sources, this is the rule to start with:
nodebench.search_public_sources is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every nodebench.search_public_sources call is checked against it from then on.
Questions about nodebench.search_public_sources
Search NodeBench public research memory and source cache for public facts about an entity. Private email, resume, and inbox text must not be sent here. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.
Register the Nodebench MCP server in PolicyLayer and add a rule for nodebench.search_public_sources: 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 Nodebench. Nothing to install.
nodebench.search_public_sources 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 nodebench.search_public_sources 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 nodebench.search_public_sources. 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.
nodebench.search_public_sources is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nodebench, and thousands of servers like it.
This server
Across the catalogue