getSpreadsheetRange
Get cells within a range from a spreadsheet (row/col coordinates).
This record as markdown: /tools/io-github-homenshum-nodebench/getspreadsheetrange.md
What getSpreadsheetRange does on Nodebench
AI agents call getSpreadsheetRange 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 getSpreadsheetRange is rated Low
This tool retrieves spreadsheet data by specifying row and column coordinates. It performs a read operation with no side effects—it does not create, modify, delete, or execute operations. Even in a context where an AI agent might abuse it (e.g., to extract sensitive financial data from a spreadsheet), the tool itself is purely a data retrieval mechanism with limited blast radius.
From the tool's definition Tool description states 'Get cells within a range from a spreadsheet' - the verb 'Get' indicates retrieval without modification. The focus on 'row/col coordinates' suggests querying specific data from an existing spreadsheet.
Attacks that exploit this kind of access
The rule that runs getSpreadsheetRange 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 getSpreadsheetRange, this is the rule to start with:
getSpreadsheetRange 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 getSpreadsheetRange call is checked against it from then on.
Questions about getSpreadsheetRange
Get cells within a range from a spreadsheet (row/col coordinates). 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 getSpreadsheetRange: 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.
getSpreadsheetRange 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 getSpreadsheetRange 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 getSpreadsheetRange. 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.
getSpreadsheetRange 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