Withdraw USDC from trading account. Requires TRADEX_KEYPAIR to be configured.
AI agents use withdraw to commit financial operations through TradeX MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool directly moves financial assets (USDC, a USD-backed stablecoin) out of a trading account. While the blast radius is somewhat contained by requiring keypair configuration, an AI agent with access could irreversibly transfer funds.
From the tool's definition Tool description explicitly states 'Withdraw USDC from trading account' - USDC is a stablecoin used to represent USD value. The server context confirms it handles 'secure transaction execution' on the Solana blockchain for trading perpetual futures.
Attacks that exploit this kind of access
Withdraw USDC from trading account. Requires TRADEX_KEYPAIR to be configured. It is categorised as a Financial tool in the TradeX MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the TradeX MCP Server MCP server in PolicyLayer and add a rule for 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 TradeX MCP Server. Nothing to install.
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 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 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.
withdraw is provided by the TradeX MCP Server MCP server (tradexcards/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →