pillar_direct_withdraw_collateral

Withdraw sBTC collateral from Zest on the Pillar smart wallet.

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/pillar-direct-withdraw-collateral.md

What pillar_direct_withdraw_collateral does on Aibtc

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

Why pillar_direct_withdraw_collateral is rated Critical

This tool moves cryptocurrency (sBTC) collateral out of a DeFi lending protocol (Zest) via a smart wallet. Withdrawing collateral is a financial operation that directly affects asset balances and positions. Misuse could drain collateral, trigger liquidations, or result in irreversible loss of funds, making it critical severity.

From the tool's definition Withdraw sBTC collateral from Zest on the Pillar smart wallet

Questions about pillar_direct_withdraw_collateral

What does the pillar_direct_withdraw_collateral tool do? +

Withdraw sBTC collateral from Zest on the Pillar smart wallet. 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 pillar_direct_withdraw_collateral? +

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

What risk level is pillar_direct_withdraw_collateral? +

pillar_direct_withdraw_collateral 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 pillar_direct_withdraw_collateral? +

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

How do I block pillar_direct_withdraw_collateral completely? +

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

What MCP server provides pillar_direct_withdraw_collateral? +

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

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