# read_text_file

Read a text file from the filesystem. Returns the file content as text.

Agent View of the PolicyLayer registry record for `read_text_file`. HTML page: https://policylayer.com/tools/deep-ai-kr-dev-mcp/read-text-file

## Facts

- Tool: `read_text_file`
- Server: Dev (`deep-ai-kr/dev-mcp`) — https://policylayer.com/tools/deep-ai-kr-dev-mcp.md
- Homepage: https://github.com/deep-ai-kr/dev-mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server rate-limited: no
- Parameters: 3
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `head` | number | no | If provided, returns only the first N lines |
| `path` | string | no | Path to the file to read (relative to root) |
| `tail` | number | no | If provided, returns only the last N lines |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "read_text_file",
    "arguments": {}
  }
}
```

## Why read_text_file is rated Low

This tool performs a simple read operation that retrieves file content without creating, modifying, deleting, or executing anything. It has no side effects and poses minimal risk even if misused by an agent—the worst outcome is information disclosure within an already-configured root directory scope. Classified as Read with low severity.

From the tool's own definition: "Tool name 'read_text_file' and description 'Read a text file from the filesystem. Returns the file content as text' clearly indicate retrieval of data with no modification or side effects."

Risk signals: Accepts file system path (path)

## Use case

AI agents call read_text_file to retrieve information from Dev without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Dev:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "read_text_file": {}
  }
}
```

## Other tools on Dev (6)

- `get_file_info` — Read — https://policylayer.com/tools/deep-ai-kr-dev-mcp/get-file-info.md
- `list_directory` — Read — https://policylayer.com/tools/deep-ai-kr-dev-mcp/list-directory.md
- `search_files` — Read — https://policylayer.com/tools/deep-ai-kr-dev-mcp/search-files.md
- `create_directory` — Write — https://policylayer.com/tools/deep-ai-kr-dev-mcp/create-directory.md
- `move_file` — Write — https://policylayer.com/tools/deep-ai-kr-dev-mcp/move-file.md
- `write_file` — Write — https://policylayer.com/tools/deep-ai-kr-dev-mcp/write-file.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=deep-ai-kr-dev-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/deep-ai-kr-dev-mcp