zest_enable_collateral
Add existing zTokens as collateral on Zest Protocol v2. Use this when you deposited directly to a vault and need to register those zTokens as collateral for borrowing. Note: zest_supply already handles this atomically via supply-collateral-add. This tool is only needed if you used vault deposit s...
This record as markdown: /tools/io-github-aibtcdev-mcp-server/zest-enable-collateral.md
What zest_enable_collateral does on Aibtc
AI agents use zest_enable_collateral to create or update resources in Aibtc, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aibtc environment.
Why zest_enable_collateral is rated Medium
This tool modifies the collateral state of existing zTokens by registering or enabling them for borrowing purposes. While it creates a new collateral relationship (Write category), it does not execute arbitrary code, delete data, or move financial assets directly—it updates a permission/status flag on the Zest Protocol.
From the tool's definition Tool description states "Add existing zTokens as collateral" and "register those zTokens as collateral for borrowing", indicating modification of collateral status on the Zest Protocol v2.
Attacks that exploit this kind of access
The rule that runs zest_enable_collateral 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 zest_enable_collateral, this is the rule to start with:
zest_enable_collateral stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every zest_enable_collateral call is checked against it from then on.
Questions about zest_enable_collateral
Add existing zTokens as collateral on Zest Protocol v2. Use this when you deposited directly to a vault and need to register those zTokens as collateral for borrowing. Note: zest_supply already handles this atomically via supply-collateral-add. This tool is only needed if you used vault deposit separately. Mainnet only. It is categorised as a Write tool in the Aibtc MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Aibtc MCP server in PolicyLayer and add a rule for zest_enable_collateral: 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.
zest_enable_collateral is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the zest_enable_collateral 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 zest_enable_collateral. 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.
zest_enable_collateral 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.
This server
Across the catalogue