Proves select fields of a certificate to a verifier.
AI agents invoke wallet_proveCertificate 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.
Proving certificate fields to a verifier involves executing a cryptographic proof operation against the BSV blockchain/wallet system. This is not purely reading data (it generates and submits a proof to an external verifier), nor does it move funds or destructively alter data. It falls under Execute as it triggers an external operation whose effects depend on the certificate fields and verifier arguments.
From the tool's definition "Proves select fields of a certificate to a verifier" — triggers an external cryptographic operation that interacts with wallet/blockchain infrastructure
Documented attack patterns abuse exactly the kind of access wallet_proveCertificate 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_proveCertificate:
{
"version": "1",
"default": "deny",
"tools": {
"wallet_proveCertificate": {
"limits": [
{
"counter": "wallet_provecertificate_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} wallet_proveCertificate 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.
Proves select fields of a certificate to a verifier. 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_proveCertificate: 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_proveCertificate 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_proveCertificate 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_proveCertificate. 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_proveCertificate 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.