Low Risk

midnight_wallet_state

Get detailed wallet state including balances, coins, and sync status. **Returns:** - tDUST balance (total and available) - Individual coin details - Pending transactions - Sync status with network **Coin Types:** - **Unshielded:** Publicly visible balance - **Shielded:** Private balance (ZK pro...

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

AI agents call midnight_wallet_state to retrieve information from Midnight Nextjs without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though midnight_wallet_state only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

midnight-next-js-mcp.yaml
tools:
  midnight_wallet_state:
    rules:
      - action: allow

See the full Midnight Nextjs policy for all 35 tools.

Tool Name midnight_wallet_state
Category Read
Risk Level Low

View all 35 tools →

What does the midnight_wallet_state tool do? +

Get detailed wallet state including balances, coins, and sync status. **Returns:** - tDUST balance (total and available) - Individual coin details - Pending transactions - Sync status with network **Coin Types:** - **Unshielded:** Publicly visible balance - **Shielded:** Private balance (ZK protected) - **Pending:** Awaiting confirmation **Use for:** - Checking available funds before operations - Debugging transaction issues - Monitoring wallet health. It is categorised as a Read tool in the Midnight Nextjs MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on midnight_wallet_state? +

Add a rule in your Intercept YAML policy under the tools section for midnight_wallet_state. 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_wallet_state? +

midnight_wallet_state is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit midnight_wallet_state? +

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

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

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