Reveals the linkage between the wallet identity and a counterparty to a verifier.
AI agents call wallet_revealCounterpartyKeyLinkage to retrieve information from Bitcoin SV MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool reveals (reads/discloses) cryptographic key linkage information between wallet identities. This is a read/disclosure operation, not a write or destructive one. However, severity is high because exposing identity linkage on a blockchain is a significant privacy risk — it could permanently de-anonymize wallet relationships, and once revealed to a verifier, that disclosure cannot be undone.
From the tool's definition Reveals the linkage between the wallet identity and a counterparty to a verifier
Documented attack patterns abuse exactly the kind of access wallet_revealCounterpartyKeyLinkage 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_revealCounterpartyKeyLinkage:
{
"version": "1",
"default": "deny",
"tools": {
"wallet_revealCounterpartyKeyLinkage": {}
}
} wallet_revealCounterpartyKeyLinkage is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Reveals the linkage between the wallet identity and a counterparty to a verifier. It is categorised as a Read tool in the Bitcoin SV MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bitcoin SV MCP Server MCP server in PolicyLayer and add a rule for wallet_revealCounterpartyKeyLinkage: 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_revealCounterpartyKeyLinkage is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the wallet_revealCounterpartyKeyLinkage 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_revealCounterpartyKeyLinkage. 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_revealCounterpartyKeyLinkage 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.