query_funding_entities
Search funding intelligence from the Convex platform. Filter by company name, round type, or get recent events. Returns structured funding data with investors, amounts, and confidence scores.
This record as markdown: /tools/io-github-homenshum-nodebench/query-funding-entities.md
What query_funding_entities does on Nodebench
AI agents call query_funding_entities 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 query_funding_entities is rated Low
This tool retrieves and queries funding data from the Convex platform without creating, modifying, deleting, or executing any side effects. The operations are purely informational (search, filter, return data), making it a Read category tool with low severity since it only accesses existing data.
From the tool's definition Tool name and description indicate a search operation: 'Search funding intelligence', 'Filter by company name', 'Returns structured funding data'. These are read-only query operations with no modification, deletion, or execution of external systems.
Attacks that exploit this kind of access
The rule that runs query_funding_entities 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 query_funding_entities, this is the rule to start with:
query_funding_entities 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 query_funding_entities call is checked against it from then on.
Questions about query_funding_entities
Search funding intelligence from the Convex platform. Filter by company name, round type, or get recent events. Returns structured funding data with investors, amounts, and confidence scores. 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 query_funding_entities: 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.
query_funding_entities 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 query_funding_entities 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 query_funding_entities. 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.
query_funding_entities 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