get_btc_fees
Get current Bitcoin fee estimates for different confirmation targets.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/get-btc-fees.md
What get_btc_fees does on Aibtc
AI agents call get_btc_fees to retrieve information from Aibtc without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_btc_fees is rated Low
This tool retrieves current Bitcoin fee data (fee estimates for different confirmation targets) without making any changes to data, executing external commands, or triggering financial transactions. It is a pure information lookup operation with no side effects.
From the tool's definition Tool name 'get_btc_fees' and description 'Get current Bitcoin fee estimates' indicate a query/retrieval operation with no modification or execution of code. Uses action verb 'Get' which is characteristic of read operations.
Attacks that exploit this kind of access
The rule that runs get_btc_fees safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aibtc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_btc_fees, this is the rule to start with:
get_btc_fees 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 Aibtc, apply this rule, and every get_btc_fees call is checked against it from then on.
Questions about get_btc_fees
Get current Bitcoin fee estimates for different confirmation targets. It is categorised as a Read tool in the Aibtc MCP Server, which means it retrieves data without modifying state.
Register the Aibtc MCP server in PolicyLayer and add a rule for get_btc_fees: 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 Aibtc. Nothing to install.
get_btc_fees 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 get_btc_fees 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 get_btc_fees. 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.
get_btc_fees is provided by the Aibtc MCP server (aibtcdev/aibtc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aibtc, and thousands of servers like it.
This server
Across the catalogue