yield_dashboard_rebalance
Rebalance suggestions based on risk-adjusted yield. Reads current positions across all protocols, compares to optimal allocation for the chosen risk tolerance, and returns actionable suggestions. Risk tolerance levels: - low: Zest 40%, ALEX 10%, Bitflow 10%, Stacking 40% - medium: Zest 45%, ALEX ...
This record as markdown: /tools/io-github-aibtcdev-mcp-server/yield-dashboard-rebalance.md
What yield_dashboard_rebalance does on Aibtc
AI agents call yield_dashboard_rebalance 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_rebalance is rated Low
This tool retrieves and analyzes wallet position data to generate rebalancing suggestions. It performs no state changes, no asset transfers, and no irreversible operations. The 'actionable suggestions' are informational output, not executed transactions. The requirement for an unlocked wallet is for read context only, not for executing changes.
From the tool's definition Tool description explicitly states 'Read-only' and 'Reads current positions across all protocols, compares to optimal allocation...
Attacks that exploit this kind of access
The rule that runs yield_dashboard_rebalance 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_rebalance, this is the rule to start with:
yield_dashboard_rebalance 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_rebalance call is checked against it from then on.
Questions about yield_dashboard_rebalance
Rebalance suggestions based on risk-adjusted yield. Reads current positions across all protocols, compares to optimal allocation for the chosen risk tolerance, and returns actionable suggestions. Risk tolerance levels: - low: Zest 40%, ALEX 10%, Bitflow 10%, Stacking 40% - medium: Zest 45%, ALEX 20%, Bitflow 15%, Stacking 20% (default) - high: Zest 50%, ALEX 30%, Bitflow 20%, Stacking 0% Read-only. Mainnet-only. Requires an unlocked wallet for address context. 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_rebalance: 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_rebalance 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_rebalance 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_rebalance. 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_rebalance 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