# get_parse_job_status

Get status for an async parse job created by submit_parse_job.

Agent View of the PolicyLayer registry record for `get_parse_job_status`. HTML page: https://policylayer.com/tools/0xpdf-mcp/get-parse-job-status

## Facts

- Tool: `get_parse_job_status`
- Server: 0xpdf (`risha-max/0xpdf-mcp`) — https://policylayer.com/tools/0xpdf-mcp.md
- Homepage: https://github.com/risha-max/0xpdf-mcp
- 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": "get_parse_job_status",
    "arguments": {}
  }
}
```

## Why get_parse_job_status is rated Low

Even though get_parse_job_status only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

## Use case

AI agents call get_parse_job_status to retrieve information from 0xpdf 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 0xpdf:

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

## Other tools on 0xpdf (12)

- `reset_mcp_runtime_metrics` — Destructive — https://policylayer.com/tools/0xpdf-mcp/reset-mcp-runtime-metrics.md
- `parse_pdf_stream` — Execute — https://policylayer.com/tools/0xpdf-mcp/parse-pdf-stream.md
- `parse_pdf_sync` — Execute — https://policylayer.com/tools/0xpdf-mcp/parse-pdf-sync.md
- `wait_for_batch_completion` — Execute — https://policylayer.com/tools/0xpdf-mcp/wait-for-batch-completion.md
- `wait_for_job_completion` — Execute — https://policylayer.com/tools/0xpdf-mcp/wait-for-job-completion.md
- `get_mcp_runtime_metrics` — Read — https://policylayer.com/tools/0xpdf-mcp/get-mcp-runtime-metrics.md
- `get_parse_batch_status` — Read — https://policylayer.com/tools/0xpdf-mcp/get-parse-batch-status.md
- `get_pricing_current` — Read — https://policylayer.com/tools/0xpdf-mcp/get-pricing-current.md
- `health_check` — Read — https://policylayer.com/tools/0xpdf-mcp/health-check.md
- `list_schemas` — Read — https://policylayer.com/tools/0xpdf-mcp/list-schemas.md
- `submit_parse_batch` — Write — https://policylayer.com/tools/0xpdf-mcp/submit-parse-batch.md
- `submit_parse_job` — Write — https://policylayer.com/tools/0xpdf-mcp/submit-parse-job.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=0xpdf-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0xpdf-mcp