Get deposit information for bridging BTC to sBTC.
AI agents call sbtc_bridge_deposit to retrieve information from Bitcoin wallet MCP server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool description says 'Get deposit information', suggesting it retrieves information about how to make a deposit rather than actually executing a transaction. However, given the server context (Bitcoin wallet with sending/financial operations) and the word 'bridging', there is some ambiguity — it could trigger an actual bridge deposit.
From the tool's definition 'Get deposit information for bridging BTC to sBTC' — the verb 'Get' indicates a read/query operation retrieving informational data
Attacks that exploit this kind of access
Get deposit information for bridging BTC to sBTC. It is categorised as a Read tool in the Bitcoin wallet MCP server MCP Server, which means it retrieves data without modifying state.
Register the Bitcoin wallet MCP server MCP server in PolicyLayer and add a rule for sbtc_bridge_deposit: 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 wallet MCP server. Nothing to install.
sbtc_bridge_deposit 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 sbtc_bridge_deposit 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 sbtc_bridge_deposit. 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.
sbtc_bridge_deposit is provided by the Bitcoin wallet MCP server MCP server (markmhendrickson/mcp-server-bitcoin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →