midnight_deploy_contract

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

// WHEN AI AGENTS USE THIS TOOL

AI agents invoke midnight_deploy_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.

// WHY ENFORCE A POLICY ON MIDNIGHT_DEPLOY_CONTRACT

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

// RECOMMENDED POLICY

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

midnight-next-js-mcp.yaml

tools:
  midnight_deploy_contract:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Midnight Nextjs policy for all 35 tools.

// DETAILS

Tool Name midnight_deploy_contract

Category Execute

MCP Server Midnight Nextjs MCP Server

Risk Level High

// MORE MIDNIGHT NEXTJS TOOLS

Financial midnight_transfer_tokens Destructive browser_eval Destructive init Destructive nextjs_call Destructive nextjs_index Execute midnight_call_contract Execute midnight_compile_contract Execute midnight_init

View all 35 tools →

// RELATED READING

// FAQ

What does the midnight_deploy_contract tool do? +

Deploy a compiled Compact smart contract to the Midnight Network. **Prerequisites:** 1. Contract must be compiled first using `midnight_compile_contract` 2. Wallet with sufficient tDUST balance for deployment 3. Network connectivity to target environment **Deployment Process:** 1. Load compiled contract artifacts 2. Initialize contract private state (if any) 3. Create deployment transaction 4. Generate ZK proof for deployment 5. Submit transaction to the network 6. Wait for confirmation **Returns:** - Contract address - Transaction hash - Block height - Deployment cost **Security:** Use `MIDNIGHT_WALLET_SEED` environment variable for wallet credentials. **Testnet Faucet:** Get free tDUST at https://faucet.testnet.midnight.network. 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.

How do I enforce a policy on midnight_deploy_contract? +

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

midnight_deploy_contract is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit midnight_deploy_contract? +

Yes. Add a rate_limit block to the midnight_deploy_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.

How do I block midnight_deploy_contract completely? +

Set action: deny in the Intercept policy for midnight_deploy_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.

What MCP server provides midnight_deploy_contract? +

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

midnight_deploy_contract

Enforce policies on Midnight Nextjs