Execute a circuit call on a deployed Midnight smart contract. **Circuit Types:** - **Public circuits:** Read-only operations that don't modify state - **Private circuits:** Operations with private witnesses and ZK proofs - **State-changing circuits:** Modify ledger state (requires wallet) **Cal...
Part of the Midnight Nextjs MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke midnight_call_contract to trigger processes or run actions in Midnight Nextjs. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
midnight_call_contract can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
midnight_call_contract:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Midnight Nextjs policy for all 35 tools.
Execute a circuit call on a deployed Midnight smart contract. **Circuit Types:** - **Public circuits:** Read-only operations that don't modify state - **Private circuits:** Operations with private witnesses and ZK proofs - **State-changing circuits:** Modify ledger state (requires wallet) **Call Process:** 1. Load contract at specified address 2. Prepare circuit arguments 3. Generate ZK proof (if required) 4. Submit transaction 5. Return result or state changes **Privacy Features:** - Private inputs are never revealed on-chain - ZK proofs validate computation without exposing data - Private state is stored locally with `private_state_id` **Example:** ``` midnight_call_contract({ contract_address: "0x123...", circuit_name: "transfer", arguments: { to: "0xabc...", amount: 100 } }) ```. It is categorised as a Execute tool in the Midnight Nextjs MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for midnight_call_contract. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Midnight Nextjs MCP server.
midnight_call_contract is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the midnight_call_contract 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_call_contract. 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_call_contract 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