# check_fax_status

Check the delivery status of a previously sent fax using its job_id. No authentication required — the job_id is the unforgeable token.

Agent View of the PolicyLayer registry record for `check_fax_status`. HTML page: https://policylayer.com/tools/com-gotfreefax-mcp/check-fax-status

## Facts

- Tool: `check_fax_status`
- Server: GotFreeFax (`https://www.gotfreefax.com/mcp`) — https://policylayer.com/tools/com-gotfreefax-mcp.md
- Homepage: https://github.com/vannet/gotfreefax-mcp
- Risk category: Read (Low risk)
- Registry record: grade D, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `job_id` | string | yes | The job ID returned by send_fax |

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": "check_fax_status",
    "arguments": {
      "job_id": "<job_id>"
    }
  }
}
```

## Why check_fax_status is rated Low

This tool retrieves the delivery status of a fax without modifying, creating, deleting, or executing any operations. It is a simple read/query operation. While the server context involves financial operations (paid faxes, credit purchases), this specific tool only checks status and does not move money or commit financial obligations.

From the tool's own definition: "Tool description states 'Check the delivery status' which is a query operation that retrieves information about a fax. No modification, deletion, or side effects occur. The tool only reads status information."

## Use case

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

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

## Other tools on GotFreeFax (6)

- `purchase_credits` — Financial — https://policylayer.com/tools/com-gotfreefax-mcp/purchase-credits.md
- `send_fax` — Financial — https://policylayer.com/tools/com-gotfreefax-mcp/send-fax.md
- `get_account_balance` — Read — https://policylayer.com/tools/com-gotfreefax-mcp/get-account-balance.md
- `list_sent_faxes` — Read — https://policylayer.com/tools/com-gotfreefax-mcp/list-sent-faxes.md
- `list_supported_formats` — Read — https://policylayer.com/tools/com-gotfreefax-mcp/list-supported-formats.md
- `send_free_fax` — Write — https://policylayer.com/tools/com-gotfreefax-mcp/send-free-fax.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=com-gotfreefax-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-gotfreefax-mcp