wallet_createSignature
Creates a digital signature using wallet keys. Supply exactly one of data or hashToDirectlySign.
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
Attacks that exploit this kind of access
The rule that runs wallet_createSignature 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_createSignature, this is the rule to start with:
wallet_createSignature stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Bitcoin SV MCP Server, apply this rule, and every wallet_createSignature call is checked against it from then on.
Questions about wallet_createSignature
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.
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.
wallet_createSignature is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
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.
Across the catalogue