wallet_getLockData
Get summary of time-locked BSV (total, unlockable, next unlock height)
This record as markdown: /tools/b-open-io-bsv-mcp/wallet-getlockdata.md
What wallet_getLockData does on Bitcoin SV MCP Server
AI agents call wallet_getLockData to retrieve information from Bitcoin SV MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why wallet_getLockData is rated Low
This tool retrieves and summarizes data about time-locked Bitcoin SV holdings (total, unlockable amounts, next unlock height). It performs no write, destructive, or financial transaction operations—it only reads the state of locked funds. The blast radius is minimal as misuse would only expose wallet lock details to the AI agent without enabling unauthorized transactions or data modification.
From the tool's definition Tool name 'wallet_getLockData' and description 'Get summary of time-locked BSV' indicate a retrieval operation that queries wallet lock information without modifying, executing, or moving funds.
Attacks that exploit this kind of access
The rule that runs wallet_getLockData 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_getLockData, this is the rule to start with:
wallet_getLockData is read-only, so it stays allowed. 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_getLockData call is checked against it from then on.
Questions about wallet_getLockData
Get summary of time-locked BSV (total, unlockable, next unlock height). 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_getLockData: 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_getLockData 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_getLockData 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_getLockData. 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_getLockData 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.
This server
Across the catalogue