searchEntities
Search entities by type, sector, or country. Returns up to 50 results.
This record as markdown: /tools/io-github-homenshum-nodebench/searchentities.md
What searchEntities does on Nodebench
AI agents call searchEntities 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 searchEntities is rated Low
This tool performs a search query to retrieve entity information filtered by type, sector, or country. The 'returns results' phrasing and lack of any mention of modification, deletion, or execution confirms this is a read-only operation with no side effects. The limited result set (50 maximum) further reduces potential blast radius. Severity is low due to passive data retrieval.
From the tool's definition Tool name 'searchEntities' and description 'Search entities by type, sector, or country. Returns up to 50 results.' indicate a query operation that retrieves data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs searchEntities 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 searchEntities, this is the rule to start with:
searchEntities 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 searchEntities call is checked against it from then on.
Questions about searchEntities
Search entities by type, sector, or country. Returns up to 50 results. 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 searchEntities: 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.
searchEntities 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 searchEntities 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 searchEntities. 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.
searchEntities 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