yield_hunter_stop

Stop autonomous yield hunting. Stops the background process that monitors and deposits sBTC. Your existing Zest positions remain untouched.

SERVERAibtc SOURCEaibtcdev/aibtc-mcp-server

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/io-github-aibtcdev-mcp-server/yield-hunter-stop.md

WHAT IT DOES

What yield_hunter_stop does on Aibtc

AI agents invoke yield_hunter_stop to trigger actions in Aibtc. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why yield_hunter_stop is rated High

This tool executes a command to stop a background process, which is an Execute-category action rather than merely Read (no querying), Write (no data creation/modification), or Destructive (the process can be restarted). The severity is medium because stopping a background process has limited blast radius—it pauses operations but doesn't delete data or cause irreversible harm.

From the tool's definition Tool description states it "Stop[s] autonomous yield hunting" and "stops the background process that monitors and deposits sBTC." This directly triggers external operations (process termination, halting deposits) whose effects depend on system state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs yield_hunter_stop 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_stop, this is the rule to start with:

yield_hunter_stop Rate-limited

yield_hunter_stop stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "yield_hunter_stop": {
      "limits": [
        {
          "counter": "yield_hunter_stop_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every yield_hunter_stop call is checked against it from then on.

FAQ

Questions about yield_hunter_stop

What does the yield_hunter_stop tool do? +

Stop autonomous yield hunting. Stops the background process that monitors and deposits sBTC. Your existing Zest positions remain untouched. It is categorised as a Execute tool in the Aibtc MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on yield_hunter_stop? +

Register the Aibtc MCP server in PolicyLayer and add a rule for yield_hunter_stop: 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.

What risk level is yield_hunter_stop? +

yield_hunter_stop is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit yield_hunter_stop? +

Yes. Add a rate_limit block to the yield_hunter_stop 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.

How do I block yield_hunter_stop completely? +

Set action: deny in the PolicyLayer policy for yield_hunter_stop. 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.

What MCP server provides yield_hunter_stop? +

yield_hunter_stop 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.

KEEP EXPLORING

More on Aibtc, and thousands of servers like it.

This server

All 358 Aibtc tools → High-risk tools on this server →

Across the catalogue

stop_emba_scan on EMBA-MCP →stop_etw_trace on Procmon → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →