crypto.btc-fees

Current Bitcoin network fee rates and mempool backlog from mempool.space. Returns recommended fee rates (sat/vByte) for fastest/half-hour/hour/economy/minimum confirmation, plus mempool size (tx count, vsize, total fees waiting). Keyless, live. The BTC counterpart to crypto.gas-oracle.

SERVERMcp SOURCE@2sio/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-2s-io-mcp/crypto.btc-fees.md

WHAT IT DOES

What crypto.btc-fees does on Mcp

AI agents call crypto.btc-fees to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why crypto.btc-fees is rated Low

This tool queries and retrieves publicly available Bitcoin network fee information and mempool statistics. It has no side effects, cannot modify state, execute transactions, or commit financial obligations. The read-only nature and lack of write/execute/financial action capabilities place it firmly in the Read category with low severity.

From the tool's definition Tool description states it 'Returns recommended fee rates...plus mempool size' — purely retrieval of current network data with no capability to modify, delete, or execute transactions.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs crypto.btc-fees safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crypto.btc-fees, this is the rule to start with:

crypto.btc-fees Allowed

crypto.btc-fees is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "crypto.btc-fees": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every crypto.btc-fees call is checked against it from then on.

FAQ

Questions about crypto.btc-fees

What does the crypto.btc-fees tool do? +

How do I enforce a policy on crypto.btc-fees? +

Register the MCP server in PolicyLayer and add a rule for crypto.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 Mcp. Nothing to install.

What risk level is crypto.btc-fees? +

crypto.btc-fees is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit crypto.btc-fees? +

Yes. Add a rate_limit block to the crypto.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.

How do I block crypto.btc-fees completely? +

Set action: deny in the PolicyLayer policy for crypto.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.

What MCP server provides crypto.btc-fees? +

crypto.btc-fees is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 572 tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →