pillar_supply
Earn yield on your Bitcoin. Supply sBTC from your Pillar smart wallet to Zest Protocol.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/pillar-supply.md
What pillar_supply does on Aibtc
AI agents use pillar_supply to commit financial operations through Aibtc, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why pillar_supply is rated Critical
This tool moves real crypto assets (sBTC/Bitcoin) from a user's smart wallet to an external DeFi protocol (Zest Protocol), committing financial obligations and transferring value. This is a financial operation with critical severity as misuse could result in significant loss of funds.
From the tool's definition Earn yield on your Bitcoin. Supply sBTC from your Pillar smart wallet to Zest Protocol.
Attacks that exploit this kind of access
The rule that runs pillar_supply 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 pillar_supply, this is the rule to start with:
Any call to pillar_supply is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every pillar_supply call is checked against it from then on.
Questions about pillar_supply
Earn yield on your Bitcoin. Supply sBTC from your Pillar smart wallet to Zest Protocol. 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.
Register the Aibtc MCP server in PolicyLayer and add a rule for pillar_supply: 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.
pillar_supply is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the pillar_supply 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 pillar_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.
pillar_supply 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.
Across the catalogue