yield_dashboard_positions
Detailed per-protocol DeFi position data. Returns an array of positions across Zest Protocol, ALEX DEX, Bitflow, and STX Stacking. Each position includes protocol, asset, value, APY, risk score, and protocol-specific details. Read-only. Mainnet-only. Requires an unlocked wallet for address contex...
This record as markdown: /tools/io-github-aibtcdev-mcp-server/yield-dashboard-positions.md
What yield_dashboard_positions does on Aibtc
AI agents call yield_dashboard_positions 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_positions is rated Low
This tool performs data retrieval and queries across DeFi protocols without creating, modifying, or deleting data. The explicit 'Read-only' designation and the nature of returning position data (protocol, asset, value, APY, risk score) confirms it is a Read operation.
From the tool's definition Tool description explicitly states 'Read-only' and returns 'Detailed per-protocol DeFi position data' with no modification capabilities. It retrieves position information across multiple protocols including Zest Protocol, ALEX DEX, Bitflow, and STX Stacking.
Attacks that exploit this kind of access
The rule that runs yield_dashboard_positions 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_positions, this is the rule to start with:
yield_dashboard_positions 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_positions call is checked against it from then on.
Questions about yield_dashboard_positions
Detailed per-protocol DeFi position data. Returns an array of positions across Zest Protocol, ALEX DEX, Bitflow, and STX Stacking. Each position includes protocol, asset, value, APY, risk score, and protocol-specific details. Read-only. Mainnet-only. Requires an unlocked wallet for address context. Known limitations: - ALEX LP and Bitflow LP: valueSats shows 0 (protocol does not expose user LP balances via read-only calls). APY is still returned. - Stacking: denominated in microSTX, not sats. 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_positions: 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_positions 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_positions 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_positions. 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_positions 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