# read_xlsx

Read content from a Microsoft Excel spreadsheet (.xlsx or .xls file). Returns the data as formatted text or JSON.

Agent View of the PolicyLayer registry record for `read_xlsx`. HTML page: https://policylayer.com/tools/deepractice-promptx/read-xlsx

## Facts

- Tool: `read_xlsx`
- Server: PromptX (`deepractice/promptx`) — https://policylayer.com/tools/deepractice-promptx.md
- Homepage: https://github.com/Deepractice/PromptX
- Risk category: Read (Low risk)
- Registry record: grade F, 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": "read_xlsx",
    "arguments": {}
  }
}
```

## Why read_xlsx is rated Low

This tool only retrieves and returns data from an Excel file in formatted text or JSON. It performs no modifications, deletions, or code execution. The blast radius of misuse is limited to potential exposure of data contained in the spreadsheet, which is a minimal security concern compared to other risk categories.

From the tool's own definition: "The tool name is 'read_xlsx' and the description explicitly states it 'Read[s] content from a Microsoft Excel spreadsheet (.xlsx or .xls file)."

## Use case

AI agents call read_xlsx to retrieve information from PromptX 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 PromptX:

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

## Other tools on PromptX (13)

- `delete_workspace_item` — Destructive — https://policylayer.com/tools/deepractice-promptx/delete-workspace-item.md
- `toolx` — Execute — https://policylayer.com/tools/deepractice-promptx/toolx.md
- `learn` — Read — https://policylayer.com/tools/deepractice-promptx/learn.md
- `list_workspace_directory` — Read — https://policylayer.com/tools/deepractice-promptx/list-workspace-directory.md
- `list_workspaces` — Read — https://policylayer.com/tools/deepractice-promptx/list-workspaces.md
- `list_xlsx_sheets` — Read — https://policylayer.com/tools/deepractice-promptx/list-xlsx-sheets.md
- `read_docx` — Read — https://policylayer.com/tools/deepractice-promptx/read-docx.md
- `read_pdf` — Read — https://policylayer.com/tools/deepractice-promptx/read-pdf.md
- `read_pptx` — Read — https://policylayer.com/tools/deepractice-promptx/read-pptx.md
- `read_workspace_file` — Read — https://policylayer.com/tools/deepractice-promptx/read-workspace-file.md
- `create_workspace_directory` — Write — https://policylayer.com/tools/deepractice-promptx/create-workspace-directory.md
- `project` — Write — https://policylayer.com/tools/deepractice-promptx/project.md
- `write_workspace_file` — Write — https://policylayer.com/tools/deepractice-promptx/write-workspace-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=deepractice-promptx · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/deepractice-promptx