wallet_verifySignature

Verifies a digital signature using wallet keys. Supply exactly one of data or hashToDirectlyVerify.

SERVERBitcoin SV MCP Server SOURCEb-open-io/bsv-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/b-open-io-bsv-mcp/wallet-verifysignature.md

WHAT IT DOES

What wallet_verifySignature does on Bitcoin SV MCP Server

AI agents call wallet_verifySignature to retrieve information from Bitcoin SV MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why wallet_verifySignature is rated Low

This tool performs signature verification, which is a pure read operation that authenticates data without creating, modifying, deleting, or executing any state-changing operations. It checks the validity of a signature against wallet keys but does not move funds, execute code, or alter blockchain state.

From the tool's definition Tool name 'wallet_verifySignature' and description 'Verifies a digital signature using wallet keys' indicate a read-only cryptographic verification operation with no data modification or state changes.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs wallet_verifySignature safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Bitcoin SV MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wallet_verifySignature, this is the rule to start with:

wallet_verifySignature Allowed

wallet_verifySignature 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": {
    "wallet_verifySignature": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Bitcoin SV MCP Server, apply this rule, and every wallet_verifySignature call is checked against it from then on.

FAQ

Questions about wallet_verifySignature

What does the wallet_verifySignature tool do? +

Verifies a digital signature using wallet keys. Supply exactly one of data or hashToDirectlyVerify. It is categorised as a Read tool in the Bitcoin SV MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on wallet_verifySignature? +

Register the Bitcoin SV MCP Server MCP server in PolicyLayer and add a rule for wallet_verifySignature: 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 Bitcoin SV MCP Server. Nothing to install.

What risk level is wallet_verifySignature? +

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

Can I rate-limit wallet_verifySignature? +

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

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

wallet_verifySignature is provided by the Bitcoin SV MCP Server MCP server (b-open-io/bsv-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Bitcoin SV MCP Server, and thousands of servers like it.

This server

All 90 Bitcoin SV MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

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