Low Risk

zest_supply

Supply assets to Zest Protocol v2. Deposits assets and adds them as collateral in one atomic operation. The supplied assets earn yield AND provide borrowing power. You can use the asset symbol (e.g., 'sBTC', 'USDC') or full contract ID. Supported assets: wSTX, sBTC, stSTX, USDC, USDH, stSTXbtc....

Part of the Aibtc MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call zest_supply 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 zest_supply 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.

io-github-aibtcdev-mcp-server.yaml
tools:
  zest_supply:
    rules:
      - action: allow

See the full Aibtc policy for all 288 tools.

Tool Name zest_supply
Category Read
MCP Server Aibtc MCP Server
Risk Level Low

View all 288 tools →

What does the zest_supply tool do? +

Supply assets to Zest Protocol v2. Deposits assets and adds them as collateral in one atomic operation. The supplied assets earn yield AND provide borrowing power. You can use the asset symbol (e.g., 'sBTC', 'USDC') or full contract ID. Supported assets: wSTX, sBTC, stSTX, USDC, USDH, stSTXbtc. Note: Zest Protocol is only available on mainnet.. It is categorised as a Read tool in the Aibtc MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on zest_supply? +

Add a rule in your Intercept YAML policy under the tools section for zest_supply. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Aibtc MCP server.

What risk level is zest_supply? +

zest_supply is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit zest_supply? +

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

How do I block zest_supply completely? +

Set action: deny in the Intercept policy for zest_supply. 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 zest_supply? +

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

Enforce policies on Aibtc

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.