yield_hunter_start
Start autonomous yield hunting. This will: 1. Monitor your wallet for sBTC 2. Automatically deposit sBTC to Zest Protocol when balance exceeds threshold 3. Keep a configurable reserve (default: 0, deposits all sBTC) 4. Wait for transaction confirmations before proceeding 5. Retry failed transacti...
This record as markdown: /tools/io-github-aibtcdev-mcp-server/yield-hunter-start.md
What yield_hunter_start does on Aibtc
AI agents use yield_hunter_start to commit financial operations through Aibtc, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why yield_hunter_start is rated Critical
This tool autonomously and continuously moves real sBTC funds from the user's wallet into a DeFi protocol on mainnet, committing financial obligations without per-transaction approval. It spans Execute and Financial categories; Financial is the most severe and most applicable given it moves crypto assets in an automated loop.
From the tool's definition Automatically deposit sBTC to Zest Protocol when balance exceeds threshold... deposits all sBTC... Run continuously until stopped... Only works on mainnet
Attacks that exploit this kind of access
The rule that runs yield_hunter_start 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_hunter_start, this is the rule to start with:
Any call to yield_hunter_start is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every yield_hunter_start call is checked against it from then on.
Questions about yield_hunter_start
Start autonomous yield hunting. This will: 1. Monitor your wallet for sBTC 2. Automatically deposit sBTC to Zest Protocol when balance exceeds threshold 3. Keep a configurable reserve (default: 0, deposits all sBTC) 4. Wait for transaction confirmations before proceeding 5. Retry failed transactions with exponential backoff 6. Run continuously until stopped Requires an unlocked wallet (use wallet_unlock first). Only works on mainnet (Zest Protocol is mainnet-only). Note: Stacks transaction fees are paid in STX, not sBTC. Default settings: - Deposit threshold: 10,000 sats (0.0001 sBTC) - Reserve: 0 sats (deposit all sBTC to maximize yield) - Check interval: 10 minutes. It is categorised as a Financial tool in the Aibtc MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Aibtc MCP server in PolicyLayer and add a rule for yield_hunter_start: 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_hunter_start is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the yield_hunter_start 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_hunter_start. 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_hunter_start 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.
Across the catalogue