fs_read
Reads a text file from the local filesystem. Supports .txt, .md, .csv, .json, .xml, .log, .yaml, .toml and common code file types. For PDFs use pdf_read, for Word use word_read, for Excel use excel_read.
This record as markdown: /tools/com-local-mcp-local-mcp/fs-read.md
What fs_read does on Local
AI agents call fs_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 file |
offset | integer | — | Start reading at this byte offset (default 0) |
max_bytes | integer | — | Maximum bytes to read (default 1 MB, max 10 MB) |
Parameters from the server's own tool schema.
Why fs_read is rated Low
This tool only retrieves data from the local filesystem without creating, modifying, deleting, or executing anything. It supports viewing text-based file formats (.txt, .md, .csv, .json, .xml, .log, .yaml, .toml, code files) but has no side effects.
From the tool's definition Tool name is 'fs_read' and description states it 'Reads a text file from the local filesystem.' The verb 'read' combined with the explicit description of retrieval-only behavior with no modification or deletion capabilities clearly indicates a read operation.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs fs_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 fs_read, this is the rule to start with:
fs_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 fs_read call is checked against it from then on.
Questions about fs_read
Reads a text file from the local filesystem. Supports .txt, .md, .csv, .json, .xml, .log, .yaml, .toml and common code file types. For PDFs use pdf_read, for Word use word_read, for Excel use excel_read. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
fs_read accepts 3 parameters: path, offset, max_bytes. 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 fs_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.
fs_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 fs_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 fs_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.
fs_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