prepare_morpho_withdraw
Build an unsigned Morpho Blue withdraw transaction (withdraws supplied loan token). Explicit amount only — "max" is not supported; query your position first.
This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/prepare-morpho-withdraw.md
What prepare_morpho_withdraw does on VaultPilot MCP
AI agents use prepare_morpho_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 |
|---|---|---|---|
chain | string | — | EVM chain Morpho Blue is deployed on. Currently only ethereum is enabled. |
amount | string | Yes | Human-readable decimal amount, NOT raw wei/base units. Example: "10" for 10 USDC. Pass "max" for full-balance withdraw/repay. |
wallet | string | Yes | 0x-prefixed EVM wallet address (40 hex chars) that will execute this action. |
marketId | string | Yes | Morpho Blue market id — 32-byte hex (0x + 64 hex chars). Identifies the market's (loanToken, collateralToken, oracle, irm, lltv) tuple. Discover via get_morpho_ |
Parameters from the server's own tool schema.
Why prepare_morpho_withdraw is rated Critical
This tool builds a transaction to withdraw supplied loan tokens from the Morpho Blue DeFi protocol. Even though it produces an unsigned transaction (requiring a separate signing step), it initiates a financial operation that moves crypto assets. The blast radius is high because an AI agent could prepare a withdrawal draining a user's lending position.
From the tool's definition 'withdraw transaction' and 'withdraws supplied loan token' — moves crypto assets out of a Morpho Blue lending position
Attacks that exploit this kind of access
The rule that runs prepare_morpho_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_morpho_withdraw, this is the rule to start with:
Any call to prepare_morpho_withdraw is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect VaultPilot MCP, apply this rule, and every prepare_morpho_withdraw call is checked against it from then on.
Questions about prepare_morpho_withdraw
Build an unsigned Morpho Blue withdraw transaction (withdraws supplied loan token). Explicit amount only — "max" is not supported; query your position first. 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.
prepare_morpho_withdraw accepts 4 parameters: chain, amount, wallet, marketId. Required: amount, wallet, marketId. The full parameter table on this page comes from the server's own tool schema.
Register the VaultPilot MCP server in PolicyLayer and add a rule for prepare_morpho_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.
prepare_morpho_withdraw 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 prepare_morpho_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.
Set action: deny in the PolicyLayer policy for prepare_morpho_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.
prepare_morpho_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.
More on VaultPilot, and thousands of servers like it.
Across the catalogue