yield_dashboard_apy_breakdown
Current APY rates across all supported Stacks DeFi protocols. Returns live APY data for Zest Protocol (sBTC lending), ALEX DEX (aBTC/STX LP), Bitflow (sBTC LP), and STX Stacking. No wallet required — pure market data. Data sources: - Zest Protocol: on-chain reserve state (current-liquidity-rate, ...
This record as markdown: /tools/io-github-aibtcdev-mcp-server/yield-dashboard-apy-breakdown.md
What yield_dashboard_apy_breakdown does on Aibtc
AI agents call yield_dashboard_apy_breakdown 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 yield_dashboard_apy_breakdown is rated Low
This tool purely queries and retrieves market data (APY rates) from DeFi protocols and APIs. There are no side effects, no state changes, no code execution, and no financial transactions. It is a straightforward read operation that gathers publicly available pricing information. The low severity reflects minimal risk even if misused by an AI agent—an agent cannot cause harm by reading APY data.
From the tool's definition Tool description states 'Current APY rates across all supported Stacks DeFi protocols' and 'No wallet required — pure market data.' It retrieves live and static APY data from on-chain sources and public APIs without modifying, executing code, or creating…
Attacks that exploit this kind of access
The rule that runs yield_dashboard_apy_breakdown 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 yield_dashboard_apy_breakdown, this is the rule to start with:
yield_dashboard_apy_breakdown 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 yield_dashboard_apy_breakdown call is checked against it from then on.
Questions about yield_dashboard_apy_breakdown
Current APY rates across all supported Stacks DeFi protocols. Returns live APY data for Zest Protocol (sBTC lending), ALEX DEX (aBTC/STX LP), Bitflow (sBTC LP), and STX Stacking. No wallet required — pure market data. Data sources: - Zest Protocol: on-chain reserve state (current-liquidity-rate, Ray units) - ALEX DEX: static 3.5% estimate (pool data available but per-user APY not live) - Bitflow: public API at app.bitflow.finance/api/pools (fallback: 2.8% estimate) - STX Stacking: static 8.0% estimate Mainnet data only (contract addresses are mainnet-specific). 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 yield_dashboard_apy_breakdown: 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.
yield_dashboard_apy_breakdown 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 yield_dashboard_apy_breakdown 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 yield_dashboard_apy_breakdown. 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.
yield_dashboard_apy_breakdown 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