nodebench.expand_resource
Expand a Nodebench resource URI (nodebench://org/{key}) by one ring using the requested lens + depth. Returns cards, evidence refs, and next-hop URIs shaped for recursive exploration.
This record as markdown: /tools/io-github-homenshum-nodebench/nodebench.expand-resource.md
What nodebench.expand_resource does on Nodebench
AI agents call nodebench.expand_resource 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.expand_resource is rated Low
The tool retrieves and expands data from a resource URI, returning structured information (cards, evidence refs, next-hop URIs) without modifying, deleting, or executing external operations. The verb 'expand' and return of 'cards' and 'refs' indicate read-only traversal/querying of a data structure. No side effects, irreversible actions, code execution, or financial operations are described or implied.
From the tool's definition Expand a Nodebench resource URI by one ring using the requested lens + depth. Returns cards, evidence refs, and next-hop URIs shaped for recursive exploration.
Attacks that exploit this kind of access
The rule that runs nodebench.expand_resource 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.expand_resource, this is the rule to start with:
nodebench.expand_resource 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.expand_resource call is checked against it from then on.
Questions about nodebench.expand_resource
Expand a Nodebench resource URI (nodebench://org/{key}) by one ring using the requested lens + depth. Returns cards, evidence refs, and next-hop URIs shaped for recursive exploration. 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.expand_resource: 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.expand_resource 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.expand_resource 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.expand_resource. 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.expand_resource 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