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%, ...
Part of the Aibtc MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call yield_dashboard_rebalance to retrieve information from Aibtc without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though yield_dashboard_rebalance only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
yield_dashboard_rebalance:
rules:
- action: allowSee the full Aibtc policy for all 288 tools.
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.
Add a rule in your Intercept YAML policy under the tools section for yield_dashboard_rebalance. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Aibtc MCP server.
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 Intercept 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 Intercept 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 (@aibtc/mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept