nodebench_search_views
Search for views by keyword — matches against titles, descriptions, tags, and tool categories. Use this to find the right view for a task.
This record as markdown: /tools/io-github-homenshum-nodebench/nodebench-search-views.md
What nodebench_search_views does on Nodebench
AI agents call nodebench_search_views 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_views is rated Low
The tool retrieves and queries existing data (views, their metadata) to help locate relevant resources. It performs read-only matching against existing information without side effects, fitting the 'Read' category. Severity is low because search operations have minimal blast radius—worst case is returning irrelevant results or all results, with no ability to modify data or trigger external actions.
From the tool's definition Tool description states 'Search for views by keyword — matches against titles, descriptions, tags, and tool categories.' This is a pure search/query operation with no data modification, deletion, or external execution.
Attacks that exploit this kind of access
The rule that runs nodebench_search_views 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_views, this is the rule to start with:
nodebench_search_views 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_views call is checked against it from then on.
Questions about nodebench_search_views
Search for views by keyword — matches against titles, descriptions, tags, and tool categories. Use this to find the right view 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 nodebench_search_views: 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_views 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_views 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_views. 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_views 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