Critical-risk tools in Midnight Nextjs
5 of the 35 tools in Midnight Nextjs are classified as critical risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.
Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.
Tools at critical risk
-
browser_evalDestructiveAutomate and test web applications using Playwright browser automation. This tool connects to playwright-mcp server and provides access to all Playwright capabilities. CRITICAL...
-
initDestructive⚠️ CALL THIS FIRST - Initialize Next.js DevTools MCP context and establish MANDATORY documentation requirements. **IMPORTANT: This tool MUST be called at the START of every Nex...
-
nextjs_callDestructiveCall a specific MCP tool on a running Next.js development server. REQUIREMENTS: - Port number of the target Next.js dev server - Tool name to execute - Optional arguments objec...
-
nextjs_indexDestructiveDiscover all running Next.js development servers and list their available MCP tools. WHEN TO USE THIS TOOL - Use proactively in these scenarios: 1. **Before implementing ANY c...
-
midnight_transfer_tokensFinancialTransfer tDUST tokens to another address. **Transfer Types:** - **Standard:** Public transfer visible on-chain - **Shielded:** Private transfer using ZK proofs **Requirements:...
Attacks that target this class
Critical-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.