Critical Risk

midnight_transfer_tokens

Transfer tDUST tokens to another address. **Transfer Types:** - **Standard:** Public transfer visible on-chain - **Shielded:** Private transfer using ZK proofs **Requirements:** - Wallet with sufficient balance - Network connectivity - Gas for transaction fees **Fees:** - Standard transfer: ~0...

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

midnight-nextjs-mcp Financial Risk 5/5

AI agents use midnight_transfer_tokens to initiate financial transactions through Midnight Nextjs. 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.

midnight_transfer_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.

midnight-next-js-mcp.yaml
tools:
  midnight_transfer_tokens:
    rules:
      - action: deny
        reason: "Requires human approval"

See the full Midnight Nextjs policy for all 35 tools.

Tool Name midnight_transfer_tokens
Category Financial
Risk Level Critical

View all 35 tools →

What does the midnight_transfer_tokens tool do? +

Transfer tDUST tokens to another address. **Transfer Types:** - **Standard:** Public transfer visible on-chain - **Shielded:** Private transfer using ZK proofs **Requirements:** - Wallet with sufficient balance - Network connectivity - Gas for transaction fees **Fees:** - Standard transfer: ~0.001 tDUST - Shielded transfer: ~0.005 tDUST (proof generation) **Security:** Use `MIDNIGHT_WALLET_SEED` environment variable.. It is categorised as a Financial tool in the Midnight Nextjs MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on midnight_transfer_tokens? +

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

What risk level is midnight_transfer_tokens? +

midnight_transfer_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 midnight_transfer_tokens? +

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

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

midnight_transfer_tokens is provided by the Midnight Nextjs MCP server (midnight-nextjs-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Midnight Nextjs

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.