New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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...

SERVERFreeSign — Free e-signature SOURCEhttps://free-sign.com/mcp
Low RISK CLASS
Category Read
Parameters 22 required
Recommended Allowedsee the rule below
Registry record Grade C, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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.

Questions about get_ots_proof

What does the get_ots_proof tool do? +

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.

What parameters does get_ots_proof accept? +

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.

How do I enforce a policy on get_ots_proof? +

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.

What risk level is get_ots_proof? +

get_ots_proof is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_ots_proof? +

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.

How do I block get_ots_proof completely? +

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.

What MCP server provides get_ots_proof? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of FreeSign — Free e-signature's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.