withdraw_usdc
Withdraw USDC to an external Base network address
This record as markdown: /tools/io-github-bbrainfrance-midas-protocol/withdraw-usdc.md
What withdraw_usdc does on MIDAS Protocol
AI agents use withdraw_usdc to commit financial operations through MIDAS Protocol, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
amount | number | Yes | |
toAddress | string | Yes |
Parameters from the server's own tool schema.
Why withdraw_usdc is rated Critical
This tool directly moves financial assets (USDC cryptocurrency) from the system to an external address. This is an irreversible financial transaction that commits the AI agent to transferring money. Even with proper controls, misuse could result in unauthorized fund transfers.
From the tool's definition Tool name 'withdraw_usdc' explicitly performs cryptocurrency withdrawal. Description states 'Withdraw USDC to an external Base network address' — a direct money movement operation. USDC is a stablecoin representing real financial value.
Attacks that exploit this kind of access
The rule that runs withdraw_usdc safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MIDAS Protocol, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For withdraw_usdc, this is the rule to start with:
Any call to withdraw_usdc is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect MIDAS Protocol, apply this rule, and every withdraw_usdc call is checked against it from then on.
Questions about withdraw_usdc
Withdraw USDC to an external Base network address. It is categorised as a Financial tool in the MIDAS Protocol MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
withdraw_usdc accepts 2 parameters: amount, toAddress. Required: amount, toAddress. The full parameter table on this page comes from the server's own tool schema.
Register the MIDAS Protocol MCP server in PolicyLayer and add a rule for withdraw_usdc: 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 MIDAS Protocol. Nothing to install.
withdraw_usdc 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 withdraw_usdc 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 withdraw_usdc. 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.
withdraw_usdc is provided by the MIDAS Protocol MCP server (https://mcp.midasprotocol.org/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MIDAS Protocol, and thousands of servers like it.
Across the catalogue