This record as markdown: /tools/io-github-homenshum-nodebench/searchdocuments.md
What searchDocuments does on Nodebench
AI agents call searchDocuments 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 searchDocuments is rated Low
This is a search/query function that retrieves documents matching search criteria. It has no side effects, does not execute code, and does not modify or delete data. It falls squarely into the Read category with low severity since full-text search over documents poses minimal security risk when misused by an AI agent.
From the tool's definition Tool name 'searchDocuments' combined with description 'Search documents by title (full-text search)' indicates a query operation that retrieves data without modifying it.
Attacks that exploit this kind of access
The rule that runs searchDocuments 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 searchDocuments, this is the rule to start with:
searchDocuments 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 searchDocuments call is checked against it from then on.
Questions about searchDocuments
Search documents by title (full-text search). 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 searchDocuments: 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.
searchDocuments 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 searchDocuments 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 searchDocuments. 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.
searchDocuments 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