# claude_read_file

Read a file from the PC filesystem. Returns the file contents as text.

Agent View of the PolicyLayer registry record for `claude_read_file`. HTML page: https://policylayer.com/tools/0motionguy-claude-bridge-mcp/claude-read-file

## Facts

- Tool: `claude_read_file`
- Server: Claude Bridge (`0motionguy/claude-bridge-mcp`) — https://policylayer.com/tools/0motionguy-claude-bridge-mcp.md
- Homepage: https://github.com/0motionguy/claude-bridge-mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

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

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

## Why claude_read_file is rated Low

The tool's sole function is to retrieve and return file contents. It does not modify, delete, execute, or move data. While it could expose sensitive information if misused, the action itself is non-destructive read-only access, making it a Read category tool with low severity.

From the tool's own definition: "Tool name is 'claude_read_file' and description states 'Read a file from the PC filesystem. Returns the file contents as text.' This is a retrieval operation with no side effects."

## Use case

AI agents call claude_read_file to retrieve information from Claude Bridge 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 Claude Bridge:

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

## Other tools on Claude Bridge (3)

- `claude_execute` — Execute — https://policylayer.com/tools/0motionguy-claude-bridge-mcp/claude-execute.md
- `claude_git_status` — Read — https://policylayer.com/tools/0motionguy-claude-bridge-mcp/claude-git-status.md
- `claude_query` — Read — https://policylayer.com/tools/0motionguy-claude-bridge-mcp/claude-query.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=0motionguy-claude-bridge-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0motionguy-claude-bridge-mcp