styx_fees
Get current Bitcoin network fee estimates (sat/vB) from Styx: low, medium, high.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/styx-fees.md
What styx_fees does on Aibtc
AI agents call styx_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 styx_fees is rated Low
This tool queries and returns data about Bitcoin network fees. It performs a read-only operation that retrieves current fee information without modifying, creating, deleting, or executing any operations. The data retrieved is informational only and has no impact on systems or financial transactions.
From the tool's definition Tool name is 'styx_fees' and description states 'Get current Bitcoin network fee estimates'. The verb 'Get' and phrase 'fee estimates' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs styx_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 styx_fees, this is the rule to start with:
styx_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 styx_fees call is checked against it from then on.
Questions about styx_fees
Get current Bitcoin network fee estimates (sat/vB) from Styx: low, medium, high. 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 styx_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.
styx_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 styx_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 styx_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.
styx_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