Estimate transaction fee for given parameters.
AI agents call btc_estimate_fee 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 performs a read-only operation—estimating fees based on parameters—with no side effects. It does not move funds (Financial), execute code (Execute), delete data (Destructive), or create/modify persistent state (Write). Fee estimation is informational and reversible by nature.
From the tool's definition Tool name and description: 'Estimate transaction fee for given parameters.' This is a query/calculation operation that returns fee estimates without creating, modifying, deleting, or executing transactions.
Attacks that exploit this kind of access
Estimate transaction fee for given parameters. 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 btc_estimate_fee: 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.
btc_estimate_fee 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 btc_estimate_fee 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 btc_estimate_fee. 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.
btc_estimate_fee 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 →