get_ots_proof
Return the .ots proof (base64) for a given OpenTimestamps anchor on an envelope. Use the official ots-cli to verify offline against Bitcoin block headers. Each seal has two anchors: kind: "byterange" commits to the signed document, kind: "signed_attrs" commits to SHA-256 of the CMS SignedAttribut...
This record as markdown: /tools/com-free-sign-signing/get-ots-proof.md
What get_ots_proof does on FreeSign — Free e-signature
AI agents call get_ots_proof 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 |
|---|---|---|---|
anchor_id | string | Yes | |
envelope_id | string | Yes |
Parameters from the server's own tool schema.
Why get_ots_proof is rated Low
Even though get_ots_proof 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.
Attacks that exploit this kind of access
The rule that runs get_ots_proof 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_ots_proof, this is the rule to start with:
get_ots_proof 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_ots_proof call is checked against it from then on.
Questions about get_ots_proof
Return the .ots proof (base64) for a given OpenTimestamps anchor on an envelope. Use the official ots-cli to verify offline against Bitcoin block headers. Each seal has two anchors: kind: "byterange" commits to the signed document, kind: "signed_attrs" commits to SHA-256 of the CMS SignedAttributes (which carry the post-quantum key commitment). It is categorised as a Read tool in the FreeSign — Free e-signature MCP Server, which means it retrieves data without modifying state.
get_ots_proof accepts 2 parameters: anchor_id, envelope_id. Required: anchor_id, 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_ots_proof: 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_ots_proof 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_ots_proof 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_ots_proof. 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_ots_proof 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