Agent modes
Chosen on the consent screen for OAuth connections (“read only”, “create drafts”, “send for signature”), or set withX-Sendforsign-Agent-Mode for header connections.
draft is the right default for most products: the agent prepares the contract and the signing links, and a human
(or your own code) sends it, or shows the links in your UI. Recipients added in draft mode are not emailed.
A blocked call returns a tool error such as
Blocked by policy: this connection is in draft mode (X-Sendforsign-Agent-Mode)..., which tells the agent to hand
over to a human instead of retrying.
Explicit confirmation
send_for_signature and archive_contract require the argument confirm: true. Without it, they do nothing and
return:
Not executed: sending for signature needs confirm: true. Show the user exactly what will happen … and call again with confirm: true only after they explicitly approve.The tool descriptions tell the model the same thing. This is a second line of defence, not a substitute for modes: a model can still set
confirm: true on its own. If no human is in the loop, use draft mode, or let your own code
decide when to call send_for_signature. MCP clients that ask the user before tools marked openWorldHint or
destructiveHint (these two tools are) add a third line.
Recipient domain allowlist
Allowed domains entered on the consent screen, orX-Sendforsign-Allowed-Domains: customer.com,partner.org on a
header connection, make create_contract, add_recipients and
send_for_signature reject any recipient whose email is outside those domains:
Blocked by policy: recipients outside the allowed domains (customer.com, partner.org): someone@gmail.comUse it when the agent should only ever contract with known parties, for example your customer’s own staff and its existing clients.
Identity: agent and principal
For OAuth connections both come from the grant: the agent is the AI app’s registered name (for example “Claude”), and the principal is the email of the Sendforsign user who approved the connection. For header connections:X-Sendforsign-Agentnames the agent (product, version, deployment).X-Sendforsign-On-Behalf-Ofnames the person or company the agent acts for: the user who asked, or the customer account. Set it from your own authenticated session, not from anything the model says.
Audit log
Every write tool call and every blocked call is recorded, with:
Read calls that succeed are not logged. The agent’s actions for a contract are returned by
get_contract_timeline as agentActions, next to the signing events
(sent, seen, signed, fully signed).
The audit log is being rolled out.
get_connection_info returns auditLog: "on" when it is active for your
connection. Contact us to enable it or to export the log.Disconnecting an AI app
OAuth connections. Removing the Sendforsign connector in the AI app (for example Settings → Connectors in Claude) stops that app from using it. The server side of a connection ends when:- the app revokes its tokens (the server supports OAuth token revocation, RFC 7009; many apps call it when you disconnect),
- the access token expires (after 1 hour) and the refresh token is not used for 90 days, or
- a used refresh token or authorization code is presented again, which revokes the whole connection as a safety measure.