eip712_hash
EIP-712 typed-data hashing and signature check: returns encodeType, typeHash, domain separator, struct hash and the final digest a wallet signs (eth_signTypedData_v4), and with a signature recovers the signer and compares it to an expected address. Summarises common payloads (ERC-2612 Permit, EIP...
This record as markdown: /tools/com-it-scorptech-x402/eip712-hash.md
What eip712_hash does on ScorpTech x402 API
AI agents call eip712_hash to retrieve information from ScorpTech x402 API 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 |
|---|---|---|---|
address | string | — | Optional expected signer |
signature | string | — | Optional 65-byte or 64-byte signature to recover the signer |
typedData | object | Yes | The eth_signTypedData_v4 payload: {types, primaryType, domain, message} (EIP712Domain type optional, inferred from domain keys) |
Parameters from the server's own tool schema.
Why eip712_hash is rated Low
Even though eip712_hash 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 eip712_hash safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For eip712_hash, this is the rule to start with:
eip712_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 ScorpTech x402 API, apply this rule, and every eip712_hash call is checked against it from then on.
Questions about eip712_hash
EIP-712 typed-data hashing and signature check: returns encodeType, typeHash, domain separator, struct hash and the final digest a wallet signs (eth_signTypedData_v4), and with a signature recovers the signer and compares it to an expected address. Summarises common payloads (ERC-2612 Permit, EIP-3009 TransferWithAuthorization used by x402 EVM payments, Permit2) so an agent can see what it is about to sign. POST JSON body. Price: $0.003 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/eip712-hash. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
eip712_hash accepts 3 parameters: address, signature, typedData. Required: typedData. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for eip712_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 ScorpTech x402 API. Nothing to install.
eip712_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 eip712_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 eip712_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.
eip712_hash is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScorpTech x402 API, and thousands of servers like it.
This server
Across the catalogue