yield_dashboard_apy_breakdown

SERVERAibtc SOURCEaibtcdev/aibtc-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/io-github-aibtcdev-mcp-server/yield-dashboard-apy-breakdown.md

WHAT IT DOES

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.

RISK

Why yield_dashboard_apy_breakdown is rated Low

Tool retrieves live DeFi protocol yield data without side effects or access control.

From the tool's definition Current APY rates across all supported Stacks DeFi protocols. No wallet required — pure market data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Allowed

yield_dashboard_apy_breakdown 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": {
    "yield_dashboard_apy_breakdown": {}
  }
}

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

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.

FAQ

Questions about yield_dashboard_apy_breakdown

What does the yield_dashboard_apy_breakdown tool do? +

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: null — no live APY source - Bitflow: null — no public pool APY endpoint - STX Stacking: null — pox-5 rewards are sBTC, paid per signer manager 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.

How do I enforce a policy on yield_dashboard_apy_breakdown? +

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.

What risk level is yield_dashboard_apy_breakdown? +

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

Can I rate-limit yield_dashboard_apy_breakdown? +

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.

How do I block yield_dashboard_apy_breakdown completely? +

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.

What MCP server provides yield_dashboard_apy_breakdown? +

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.

KEEP EXPLORING

More on Aibtc, and thousands of servers like it.

This server

All 366 Aibtc tools →

Across the catalogue

The MCP Attack Database →

Guides

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