This record as markdown: /tools/io-github-homenshum-nodebench/nb-search-reports.md
What nb_search_reports does on Nodebench
AI agents call nb_search_reports 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 nb_search_reports is rated Low
This is a straightforward read operation that retrieves or queries existing reports and packets. The use of 'search' confirms it retrieves data without side effects. No data is created, modified, deleted, or executed. The blast radius of misuse is minimal—an agent could only access reports it is authorized to search, which is a standard read permission risk.
From the tool's definition Tool name 'nb_search_reports' and description 'Search saved reports and public packets' indicate a search/query operation with no modification or destructive capability.
Attacks that exploit this kind of access
The rule that runs nb_search_reports 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 nb_search_reports, this is the rule to start with:
nb_search_reports 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 nb_search_reports call is checked against it from then on.
Questions about nb_search_reports
Search saved reports and public packets. 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 nb_search_reports: 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.
nb_search_reports 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 nb_search_reports 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 nb_search_reports. 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.
nb_search_reports 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