findTools
Search available tools by keyword or capability description. Returns matching tool names and descriptions ranked by BM25 relevance. Use this to discover which tools are available for a task.
This record as markdown: /tools/io-github-homenshum-nodebench/findtools.md
What findTools does on Nodebench
AI agents call findTools 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 findTools is rated Low
This is a discovery/search tool that retrieves information about available tools from a registry or catalog. It performs no side effects, executes no external code, modifies no data, and has no destructive or financial impact. It purely reads and returns ranked results from an existing index. This is a standard Read classification.
From the tool's definition Tool name 'findTools' and description 'Search available tools by keyword or capability description. Returns matching tool names and descriptions ranked by BM25 relevance.' indicates a retrieval operation that queries tool metadata and returns search results…
Attacks that exploit this kind of access
The rule that runs findTools 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 findTools, this is the rule to start with:
findTools 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 findTools call is checked against it from then on.
Questions about findTools
Search available tools by keyword or capability description. Returns matching tool names and descriptions ranked by BM25 relevance. Use this to discover which tools are available for a task. 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 findTools: 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.
findTools 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 findTools 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 findTools. 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.
findTools 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