get_receipt
Return the envelope record (including final_pdf_sha256, final_signature_base64url, final_payload_json), per-signer signing receipts, and OpenTimestamps anchor metadata. Evidence only, never PDF bytes.
This record as markdown: /tools/com-free-sign-signing/get-receipt.md
What get_receipt does on FreeSign — Free e-signature
AI agents call get_receipt to retrieve information from FreeSign — Free e-signature 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 |
|---|---|---|---|
envelope_id | string | Yes |
Parameters from the server's own tool schema.
Why get_receipt is rated Low
This is a read-only query operation that retrieves cryptographic evidence and audit metadata (hashes, signatures, timestamps) associated with a signing envelope. While the data retrieved is sensitive (signature hashes, audit chain information), the tool itself performs no modification, deletion, or execution—it only queries and returns existing records.
From the tool's definition Tool returns envelope records, signing receipts, and metadata ('Return the envelope record...per-signer signing receipts, and OpenTimestamps anchor metadata'). Explicitly states 'Evidence only, never PDF bytes' — retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get_receipt safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FreeSign — Free e-signature, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_receipt, this is the rule to start with:
get_receipt 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 FreeSign — Free e-signature, apply this rule, and every get_receipt call is checked against it from then on.
Questions about get_receipt
Return the envelope record (including final_pdf_sha256, final_signature_base64url, final_payload_json), per-signer signing receipts, and OpenTimestamps anchor metadata. Evidence only, never PDF bytes. It is categorised as a Read tool in the FreeSign — Free e-signature MCP Server, which means it retrieves data without modifying state.
get_receipt accepts 1 parameter: envelope_id. Required: envelope_id. The full parameter table on this page comes from the server's own tool schema.
Register the FreeSign — Free e-signature MCP server in PolicyLayer and add a rule for get_receipt: 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 FreeSign — Free e-signature. Nothing to install.
get_receipt 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 get_receipt 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 get_receipt. 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.
get_receipt is provided by the FreeSign — Free e-signature MCP server (https://free-sign.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FreeSign — Free e-signature, and thousands of servers like it.
This server
Across the catalogue