verify_document_hash
Find FreeSign receipts matching a local document SHA-256 hash.
This record as markdown: /tools/com-free-sign-signing/verify-document-hash.md
What verify_document_hash does on FreeSign — Free e-signature
AI agents call verify_document_hash 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 |
|---|---|---|---|
document_sha256 | string | Yes |
Parameters from the server's own tool schema.
Why verify_document_hash is rated Low
This tool performs a read-only lookup of existing signing receipts. It retrieves data without modifying, deleting, or executing operations. The hash lookup is a search operation analogous to a database query. Even though the server handles e-signatures (legally significant), this specific tool only reads/verifies records rather than creating signatures or financial transactions.
From the tool's definition Tool description states 'Find FreeSign receipts matching a local document SHA-256 hash' — a pure query/lookup operation that retrieves matching receipts based on a hash input.
Attacks that exploit this kind of access
The rule that runs verify_document_hash 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 verify_document_hash, this is the rule to start with:
verify_document_hash 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 verify_document_hash call is checked against it from then on.
Questions about verify_document_hash
Find FreeSign receipts matching a local document SHA-256 hash. It is categorised as a Read tool in the FreeSign — Free e-signature MCP Server, which means it retrieves data without modifying state.
verify_document_hash accepts 1 parameter: document_sha256. Required: document_sha256. 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 verify_document_hash: 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.
verify_document_hash 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 verify_document_hash 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 verify_document_hash. 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.
verify_document_hash 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