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.
This record as markdown: /tools/com-gotfreefax-mcp/check-fax-status.md
What check_fax_status does on GotFreeFax
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
job_id | string | Yes | The job ID returned by send_fax |
Parameters from the server's own tool schema.
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 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.
Attacks that exploit this kind of access
The rule that runs check_fax_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GotFreeFax, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_fax_status, this is the rule to start with:
check_fax_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GotFreeFax, apply this rule, and every check_fax_status call is checked against it from then on.
Questions about 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. It is categorised as a Read tool in the GotFreeFax MCP Server, which means it retrieves data without modifying state.
check_fax_status accepts 1 parameter: job_id. Required: job_id. The full parameter table on this page comes from the server's own tool schema.
Register the GotFreeFax MCP server in PolicyLayer and add a rule for check_fax_status: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches GotFreeFax. Nothing to install.
check_fax_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the check_fax_status rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for check_fax_status. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
check_fax_status is provided by the GotFreeFax MCP server (https://www.gotfreefax.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GotFreeFax, and thousands of servers like it.
This server
Across the catalogue