prepare_compound_withdraw

Build an unsigned Compound V3 withdraw transaction. Pass amount: "max" to withdraw the full supplied balance.

SERVERVaultPilot MCP SOURCEvaultpilot-mcp

Critical RISK CLASS

Category Financial

Parameters 54 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/prepare-compound-withdraw.md

WHAT IT DOES

What prepare_compound_withdraw does on VaultPilot MCP

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

Parameter	Type	Required	Description
`asset`	string	Yes	ERC-20 token address being supplied or withdrawn — either the market's base token or a listed collateral token.
`chain`	string	—	EVM chain the Comet market lives on. Defaults to ethereum.
`amount`	string	Yes	Human-readable decimal amount of `asset`, NOT raw wei/base units. Example: "10" for 10 USDC. Pass "max" for full-balance withdraw.
`market`	string	Yes	Comet market address (e.g. cUSDCv3). Discover via get_compound_positions or the Compound registry.
`wallet`	string	Yes	0x-prefixed EVM wallet address (40 hex chars) that will execute this action.

Parameters from the server's own tool schema.

RISK

Why prepare_compound_withdraw is rated Critical

This tool prepares a transaction to withdraw crypto assets from a Compound V3 lending position. While it only builds an unsigned transaction (not yet broadcast), it is a direct precursor to a financial operation that moves crypto assets. In a self-custodial AI agent context, a signing step may follow automatically.

From the tool's definition 'Build an unsigned Compound V3 withdraw transaction' and 'withdraw the full supplied balance' — directly prepares a DeFi financial withdrawal from Compound V3 lending protocol

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs prepare_compound_withdraw safely

PolicyLayer is an MCP gateway: it sits between your AI agents and VaultPilot MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For prepare_compound_withdraw, this is the rule to start with:

prepare_compound_withdraw Approval-gated

Any call to prepare_compound_withdraw is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "prepare_compound_withdraw": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect VaultPilot MCP, apply this rule, and every prepare_compound_withdraw call is checked against it from then on.

FAQ

Questions about prepare_compound_withdraw

What does the prepare_compound_withdraw tool do? +

Build an unsigned Compound V3 withdraw transaction. Pass amount: "max" to withdraw the full supplied balance. It is categorised as a Financial tool in the VaultPilot MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

What parameters does prepare_compound_withdraw accept? +

prepare_compound_withdraw accepts 5 parameters: asset, chain, amount, market, wallet. Required: asset, amount, market, wallet. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on prepare_compound_withdraw? +

Register the VaultPilot MCP server in PolicyLayer and add a rule for prepare_compound_withdraw: 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 VaultPilot MCP. Nothing to install.

What risk level is prepare_compound_withdraw? +

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

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

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

prepare_compound_withdraw is provided by the VaultPilot MCP server (vaultpilot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on VaultPilot, and thousands of servers like it.

This server

All 189 VaultPilot tools → Critical-risk tools on this server →

Across the catalogue

build_redeem_withdraw_tx on Atv → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →