New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

wallet_createSignature

Creates a digital signature using wallet keys. Supply exactly one of data or hashToDirectlySign.

SERVERBitcoin SV MCP Server SOURCEb-open-io/bsv-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

What wallet_createSignature does on Bitcoin SV MCP Server

AI agents invoke wallet_createSignature to trigger actions in Bitcoin SV MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why wallet_createSignature is rated High

This tool performs a cryptographic signing operation using private wallet keys. It does not move funds (Financial) or delete data (Destructive), but it executes a key operation that produces a cryptographic artifact (signature) with real-world implications — signatures can authorize transactions or actions on the blockchain.

From the tool's definition Creates a digital signature using wallet keys

Questions about wallet_createSignature

What does the wallet_createSignature tool do? +

Creates a digital signature using wallet keys. Supply exactly one of data or hashToDirectlySign. It is categorised as a Execute tool in the Bitcoin SV MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on wallet_createSignature? +

Register the Bitcoin SV MCP Server MCP server in PolicyLayer and add a rule for wallet_createSignature: 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_createSignature? +

wallet_createSignature is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit wallet_createSignature? +

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

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Bitcoin SV MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.