Check the health status of Midnight Network services. Returns the status of: - Indexer (GraphQL API for blockchain data) - Proof Server (ZK proof generation) - Node RPC (transaction submission) - Current block height - Network ID Use this tool to: - Verify network connectivity before operations...
Part of the Midnight Nextjs MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call midnight_network_status 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_network_status 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.
tools:
midnight_network_status:
rules:
- action: allowSee the full Midnight Nextjs policy for all 35 tools.
Check the health status of Midnight Network services. Returns the status of: - Indexer (GraphQL API for blockchain data) - Proof Server (ZK proof generation) - Node RPC (transaction submission) - Current block height - Network ID Use this tool to: - Verify network connectivity before operations - Debug connection issues - Check service latency. It is categorised as a Read tool in the Midnight Nextjs MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for midnight_network_status. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Midnight Nextjs MCP server.
midnight_network_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the midnight_network_status 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.
Set action: deny in the Intercept policy for midnight_network_status. 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.
midnight_network_status 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.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept