evm_verify_signature

SERVERScorpTech x402 API SOURCEhttps://scorptech.it.com/api/x402/mcp

Low RISK CLASS

Category Read

Parameters 51 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-it-scorptech-x402/evm-verify-signature.md

WHAT IT DOES

What evm_verify_signature does on ScorpTech x402 API

AI agents call evm_verify_signature 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
`hash`	string	—	Raw 32-byte digest that was signed (no prefix added), e.g. an EIP-712 digest
`address`	string	—	Expected signer, to get match true/false
`message`	string	—	Signed message for personal_sign (EIP-191); give message or hash
`signature`	string	Yes	0x signature: 65 bytes r,s,v or 64 bytes EIP-2098
`messageEncoding`	string	—	How to read message: UTF-8 text or 0x-hex bytes

Parameters from the server's own tool schema.

RISK

Why evm_verify_signature is rated Low

Even though evm_verify_signature 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

RECOMMENDED RULE

The rule that runs evm_verify_signature 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 evm_verify_signature, this is the rule to start with:

evm_verify_signature Allowed

evm_verify_signature is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "evm_verify_signature": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ScorpTech x402 API, apply this rule, and every evm_verify_signature call is checked against it from then on.

FAQ

Questions about evm_verify_signature

What does the evm_verify_signature tool do? +

Verify an Ethereum signature offline: recovers the signer address (secp256k1 ecrecover) from an EIP-191 personal_sign message (UTF-8 or hex) or a raw 32-byte digest (e.g. an EIP-712 hash), compares it with an expected address, flags malleable high-s signatures, accepts 65-byte r,s,v and 64-byte EIP-2098 compact signatures, and parses Sign-In with Ethereum (EIP-4361) messages (domain, nonce, chain, expiry). For smart-contract wallets (EIP-1271) recovery does not apply. Price: $0.003 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/evm-verify-signature. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.

What parameters does evm_verify_signature accept? +

evm_verify_signature accepts 5 parameters: hash, address, message, signature, messageEncoding. Required: signature. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on evm_verify_signature? +

Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for evm_verify_signature: 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.

What risk level is evm_verify_signature? +

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

Can I rate-limit evm_verify_signature? +

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

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

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

KEEP EXPLORING

More on ScorpTech x402 API, and thousands of servers like it.

This server

All 1012 ScorpTech x402 API tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →