yield_dashboard_overview
Portfolio overview across Stacks DeFi protocols. Aggregates positions across Zest Protocol (sBTC lending), ALEX DEX (AMM LP), Bitflow (DEX LP), and STX Stacking. Returns total value, weighted APY, and per-protocol breakdown. Read-only. Mainnet-only. Requires an unlocked wallet for address context...
This record as markdown: /tools/io-github-aibtcdev-mcp-server/yield-dashboard-overview.md
What yield_dashboard_overview does on Aibtc
AI agents call yield_dashboard_overview 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_overview is rated Low
This tool queries and aggregates existing portfolio data across multiple DeFi protocols (Zest Protocol, ALEX DEX, Bitflow, STX Stacking) without creating, modifying, deleting, or executing any transactions. The explicit 'Read-only' designation and aggregation-only functionality clearly place it in the Read category.
From the tool's definition Tool description explicitly states 'Read-only' and 'Portfolio overview' which retrieves and aggregates data across DeFi protocols without modification. Returns 'total value, weighted APY, and per-protocol breakdown' with no side effects.
Attacks that exploit this kind of access
The rule that runs yield_dashboard_overview 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_overview, this is the rule to start with:
yield_dashboard_overview 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_overview call is checked against it from then on.
Questions about yield_dashboard_overview
Portfolio overview across Stacks DeFi protocols. Aggregates positions across Zest Protocol (sBTC lending), ALEX DEX (AMM LP), Bitflow (DEX LP), and STX Stacking. Returns total value, weighted APY, and per-protocol breakdown. Read-only. Mainnet-only. Requires an unlocked wallet for address context. Note: ALEX LP and Bitflow LP position values are 0 — these protocols do not expose user LP positions via read-only calls. APY figures are still returned. 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_overview: 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_overview 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_overview 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_overview. 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_overview 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