Critical Risk →

withdraw

Sweep funds out of the calling agent's Privy wallet to any address. WHAT IT DOES: builds and signs a Solana transfer (native SOL or any SPL/Token-2022 mint) from the agent's broker-managed wallet to to. Broker submits the tx; on confirmation it returns the signature. WHEN TO USE: - Retiring an ag...

Risk signalsHandles credentials or secrets (api_key)

Part of the Fomox402 server.

withdraw can move real money through Fomox402, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE FOMOX402 →

Free to start. No card required.

AI agents use withdraw to initiate financial transactions through Fomox402. Financial operations involve real money and are irreversible once processed. PolicyLayer blocks financial tools by default, requiring explicit human approval with transaction-level limits to prevent unauthorised spending.

withdraw moves real money. Without a policy, an autonomous agent could initiate transactions that drain accounts or exceed budgets. PolicyLayer blocks financial tools by default, requiring human-in-the-loop approval with configurable spending limits per transaction and per time window.

Financial tools involve real money. Block by default and require explicit human approval before enabling.

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

See the full Fomox402 policy for all 25 tools.

Get this rule live on your own Fomox402 server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY FOMOX402 →

View all 25 tools →

These attack patterns abuse exactly the kind of access withdraw gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so withdraw only ever does what you allow.

SECURE FOMOX402 →

Other financial tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the withdraw tool do? +

Sweep funds out of the calling agent's Privy wallet to any address. WHAT IT DOES: builds and signs a Solana transfer (native SOL or any SPL/Token-2022 mint) from the agent's broker-managed wallet to to. Broker submits the tx; on confirmation it returns the signature. WHEN TO USE: - Retiring an agent and reclaiming its funds - Cashing out winnings to a long-term wallet - Routing $fomox402 to an exchange / Jupiter / etc. ASSET PARAMETER: - 'sol' → native SOL, in lamports (amountRaw='all' keeps a 5000-lamport reserve so the transfer tx itself can pay its own fee) - any base58 mint pubkey → that token's ATA. amountRaw='all' sweeps the full balance (closes ATA if balance hits 0 after sweep). Token-2022 mints are auto-detected by the broker. AUTHORITY: the api_key. Same auth model as place_bid — anyone with the key can move funds. Lose the key = lose the wallet. Withdraw is the intentional escape hatch. RETURNS: { tx (Solana sig), to, asset, amountRaw_sent, balance_after }. FAILURE MODES: withdraw_failed (insufficient_balance) — wallet doesn't have that much withdraw_failed (invalid_destination) — to isn't a valid pubkey withdraw_failed (rpc) — Solana RPC, retry RELATED: get_me (check balances first), topup (the opposite — bring funds in).. It is categorised as a Financial tool in the Fomox402 MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on withdraw? +

Register the Fomox402 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 Fomox402. Nothing to install.

What risk level is withdraw? +

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

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.

How do I block withdraw completely? +

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.

What MCP server provides withdraw? +

withdraw is provided by the Fomox402 MCP server (https://bot.staccpad.fun/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Fomox402 tool call.

Deterministic rules across all 25 Fomox402 tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.