list_sent_faxes
List faxes previously sent by the authenticated account (most recent first). Includes faxes sent via MCP, REST API, and the prepaid web form. Free anonymous sends are not included.
This record as markdown: /tools/com-gotfreefax-mcp/list-sent-faxes.md
What list_sent_faxes does on GotFreeFax
AI agents call list_sent_faxes 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 |
|---|---|---|---|
limit | integer | — | Max records to return (1-100, default 20) |
offset | integer | — | Skip first N records for pagination (default 0) |
Parameters from the server's own tool schema.
Why list_sent_faxes is rated Low
This tool retrieves and queries existing fax history data without modifying, deleting, or executing any operations. It is a pure read operation with minimal blast radius—even if misused by an agent, it only exposes historical metadata about the account's past fax activity, not financial transactions or destructive operations.
From the tool's definition Tool name 'list_sent_faxes' and description 'List faxes previously sent' indicate a retrieval operation with no side effects. The description explicitly states it queries historical data (faxes already sent).
Attacks that exploit this kind of access
The rule that runs list_sent_faxes 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 list_sent_faxes, this is the rule to start with:
list_sent_faxes 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 list_sent_faxes call is checked against it from then on.
Questions about list_sent_faxes
List faxes previously sent by the authenticated account (most recent first). Includes faxes sent via MCP, REST API, and the prepaid web form. Free anonymous sends are not included. It is categorised as a Read tool in the GotFreeFax MCP Server, which means it retrieves data without modifying state.
list_sent_faxes accepts 2 parameters: limit, offset. 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 list_sent_faxes: 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.
list_sent_faxes 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 list_sent_faxes 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 list_sent_faxes. 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.
list_sent_faxes 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