excel_read
Reads data from an Excel (.xlsx) file. Returns sheets and cell values.
This record as markdown: /tools/com-local-mcp-local-mcp/excel-read.md
What excel_read does on Local
AI agents call excel_read to retrieve information from Local without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Absolute path to the .xlsx file |
max_rows | integer | — | Max rows to return (default 100) |
sheet_name | string | — | Sheet name to read (optional, reads first sheet) |
Parameters from the server's own tool schema.
Why excel_read is rated Low
This tool performs a read-only operation on Excel files. It retrieves and returns data (sheets and cell values) without creating, modifying, deleting, or executing any operations. This is a classic Read operation with minimal risk—the only concern would be unauthorized access to sensitive data contained within files, but the tool itself poses no destructive or side-effect risk.
From the tool's definition Tool name 'excel_read' and description 'Reads data from an Excel (.xlsx) file. Returns sheets and cell values.' explicitly indicate retrieval of data with no modification, deletion, or execution.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs excel_read safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For excel_read, this is the rule to start with:
excel_read 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 Local, apply this rule, and every excel_read call is checked against it from then on.
Questions about excel_read
Reads data from an Excel (.xlsx) file. Returns sheets and cell values. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
excel_read accepts 3 parameters: path, max_rows, sheet_name. Required: path. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for excel_read: 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 Local. Nothing to install.
excel_read 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 excel_read 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 excel_read. 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.
excel_read is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue