This record as markdown: /tools/io-github-homenshum-nodebench/getholdings.md
What getHoldings does on Nodebench
AI agents call getHoldings 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 getHoldings is rated Low
This tool retrieves financial holding information for an investor. While it accesses financial data, it performs no write operations, does not execute code or commands, does not delete data, and does not move money or create financial obligations. It is a straightforward read operation that queries existing data without causing state changes.
From the tool's definition Tool name is 'getHoldings' and description states 'Get all fund holdings for a given investor entity.' The verb 'get' and action 'holdings' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs getHoldings 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 getHoldings, this is the rule to start with:
getHoldings 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 getHoldings call is checked against it from then on.
Questions about getHoldings
Get all fund holdings for a given investor entity. 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 getHoldings: 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.
getHoldings 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 getHoldings 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 getHoldings. 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.
getHoldings 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