This record as markdown: /tools/io-github-homenshum-nodebench/listspreadsheets.md
What listSpreadsheets does on Nodebench
AI agents call listSpreadsheets 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 listSpreadsheets is rated Low
This tool performs a read-only operation that retrieves and presents spreadsheet metadata sorted by recency. It does not create, modify, delete, or execute any operations; it merely queries and returns user data. The blast radius is minimal as misuse would only expose metadata about the user's spreadsheets, not cause data loss or unauthorized actions.
From the tool's definition listSpreadsheets — 'List user spreadsheets sorted by last updated.' The verb 'List' indicates a query operation that retrieves data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs listSpreadsheets 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 listSpreadsheets, this is the rule to start with:
listSpreadsheets 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 listSpreadsheets call is checked against it from then on.
Questions about listSpreadsheets
List user spreadsheets sorted by last updated. 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 listSpreadsheets: 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.
listSpreadsheets 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 listSpreadsheets 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 listSpreadsheets. 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.
listSpreadsheets 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