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

create_signing_envelope

Create a FreeSign envelope from a PDF SHA-256 hash. Do not send PDF bytes. The created envelope is NOT yet session-bound — the browser that opens the returned signing_url generates an ECDSA P-256 keypair locally and POSTs the public JWK to /api/envelopes/{id}/session-bind before any protected req...

SERVERFreeSign — Free e-signature SOURCEhttps://free-sign.com/mcp
Medium RISK CLASS
Category Write
Parameters 11 required
Recommended Rate-limitedsee the rule below
Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/com-free-sign-signing/create-signing-envelope.md

What create_signing_envelope does on FreeSign — Free e-signature

AI agents use create_signing_envelope to create or update resources in FreeSign — Free e-signature, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FreeSign — Free e-signature environment.

ParameterTypeRequiredDescription
document_sha256 string Yes SHA-256 of the original PDF bytes, computed locally by the user or agent.

Parameters from the server's own tool schema.

Why create_signing_envelope is rated Medium

This tool creates a new, persistent signing envelope bound to a document hash, which modifies server state irreversibly by registering a signing session. Although the envelope itself is not session-bound until a human uses the returned URL, the creation of the envelope is a Write operation.

From the tool's definition 'Create a FreeSign envelope' — the tool creates a new signing envelope object. The description confirms this is a creation operation ('create_signing_envelope') that produces a signing_url for downstream use.

Questions about create_signing_envelope

What does the create_signing_envelope tool do? +

Create a FreeSign envelope from a PDF SHA-256 hash. Do not send PDF bytes. The created envelope is NOT yet session-bound — the browser that opens the returned signing_url generates an ECDSA P-256 keypair locally and POSTs the public JWK to /api/envelopes/{id}/session-bind before any protected request will succeed. AI agents calling this tool just hand the signing_url to a human, who continues in a browser. It is categorised as a Write tool in the FreeSign — Free e-signature MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does create_signing_envelope accept? +

create_signing_envelope accepts 1 parameter: document_sha256. Required: document_sha256. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on create_signing_envelope? +

Register the FreeSign — Free e-signature MCP server in PolicyLayer and add a rule for create_signing_envelope: 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 create_signing_envelope? +

create_signing_envelope is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_signing_envelope? +

Yes. Add a rate_limit block to the create_signing_envelope 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 create_signing_envelope completely? +

Set action: deny in the PolicyLayer policy for create_signing_envelope. 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 create_signing_envelope? +

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