Critical Risk →

prepare_withdraw

Prepare unsigned transactions to withdraw GWHF from the GrowiHFVault. Returns approve + withdraw calldata ready to sign externally. The server does NOT handle private keys.

Part of the Mcp Growi MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

mcp-growi Financial

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

prepare_withdraw moves real money. Without a policy, an autonomous agent could initiate transactions that drain accounts or exceed budgets. Intercept 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.

io-github-growi-defi-mcp-growi.yaml
tools:
  prepare_withdraw:
    rules:
      - action: deny
        reason: "Requires human approval"

See the full Mcp Growi policy for all 11 tools.

Tool Name prepare_withdraw
Category Financial
Risk Level Critical

View all 11 tools →

Agents calling financial-class tools like prepare_withdraw have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Financial risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

prepare_withdraw is one of the critical-risk operations in Mcp Growi. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the prepare_withdraw tool do? +

Prepare unsigned transactions to withdraw GWHF from the GrowiHFVault. Returns approve + withdraw calldata ready to sign externally. The server does NOT handle private keys.. It is categorised as a Financial tool in the Mcp Growi MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on prepare_withdraw? +

Add a rule in your Intercept YAML policy under the tools section for prepare_withdraw. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Mcp Growi MCP server.

What risk level is prepare_withdraw? +

prepare_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_withdraw? +

Yes. Add a rate_limit block to the prepare_withdraw rule in your Intercept 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_withdraw completely? +

Set action: deny in the Intercept policy for prepare_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_withdraw? +

prepare_withdraw is provided by the Mcp Growi MCP server (mcp-growi). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.