zest_repay

Repay borrowed assets to Zest Protocol (v0-4-market). Repays borrowed assets plus accrued interest. You can use the asset symbol (e.g.,

SERVERAibtc SOURCEaibtcdev/aibtc-mcp-server
Critical RISK CLASS
Category Financial
Parameters 00 required
Recommended Approval-gatedsee the rule below
Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/io-github-aibtcdev-mcp-server/zest-repay.md

What zest_repay does on Aibtc

AI agents use zest_repay to commit financial operations through Aibtc, usually the final step of a payment, billing, or trading workflow. A call moves real money.

Why zest_repay is rated Critical

This tool executes a financial repayment transaction on a DeFi lending protocol, moving assets (including interest) back to the protocol. It commits financial obligations and moves funds on-chain, making it a Financial category tool with critical severity due to the irreversible nature of blockchain transactions and potential for significant asset movement.

From the tool's definition Repay borrowed assets to Zest Protocol... Repays borrowed assets plus accrued interest

Questions about zest_repay

What does the zest_repay tool do? +

Repay borrowed assets to Zest Protocol (v0-4-market). Repays borrowed assets plus accrued interest. You can use the asset symbol (e.g.,. 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.

How do I enforce a policy on zest_repay? +

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

zest_repay is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit zest_repay? +

Yes. Add a rate_limit block to the zest_repay 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 zest_repay completely? +

Set action: deny in the PolicyLayer policy for zest_repay. 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_repay? +

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Aibtc's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.