Creates a digital signature using wallet keys.
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.
Creating a digital signature uses private wallet keys to sign data, which is an active cryptographic operation with real-world consequences. It can be used to authorize transactions or other blockchain actions. While not directly moving funds, signatures are a prerequisite for financial operations and misuse could lead to unauthorized authorization of actions.
From the tool's definition Creates a digital signature using wallet keys
Documented attack patterns abuse exactly the kind of access wallet_createSignature gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bitcoin SV MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for wallet_createSignature:
{
"version": "1",
"default": "deny",
"tools": {
"wallet_createSignature": {
"limits": [
{
"counter": "wallet_createsignature_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} 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.
Free to start. No card required.
Creates a digital signature using wallet keys. 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.
Start from Bitcoin SV MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
80 Bitcoin SV MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.