Critical Risk →

withdraw_tokens

Withdraw tokens from ZetaChain

Moves cryptocurrency to other chains

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

universal-blockchain-mcp Financial Risk 5/5

AI agents use withdraw_tokens to initiate financial transactions through Universal Blockchain. 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.

withdraw_tokens 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-expertvagabond-universal-blockchain.yaml
tools:
  withdraw_tokens:
    rules:
      - action: deny
        reason: "Requires human approval"

See the full Universal Blockchain policy for all 17 tools.

Tool Name withdraw_tokens
Category Financial
Risk Level Critical

View all 17 tools →

Agents calling financial-class tools like withdraw_tokens 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.

withdraw_tokens is one of the critical-risk operations in Universal Blockchain. 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 withdraw_tokens tool do? +

Withdraw tokens from ZetaChain. It is categorised as a Financial tool in the Universal Blockchain MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on withdraw_tokens? +

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

What risk level is withdraw_tokens? +

withdraw_tokens 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_tokens? +

Yes. Add a rate_limit block to the withdraw_tokens 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 withdraw_tokens completely? +

Set action: deny in the Intercept policy for withdraw_tokens. 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_tokens? +

withdraw_tokens is provided by the Universal Blockchain MCP server (universal-blockchain-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Universal Blockchain

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.