AI agents invoke launch-nuke to trigger actions in Defcon. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool executes a command that performs a consequential operation within the game environment. While this is within a game context (DEFCON), it exhibits Execute category characteristics: it runs a triggered action whose effects depend entirely on user-supplied arguments, and the outcome cannot be easily reversed during gameplay.
From the tool's definition Tool description states 'Launches a nuclear missile from a specified silo to target coordinates' — this is a direct action that triggers an external operation (missile launch) within the game with effects determined by the provided arguments (silo location,…
Attacks that exploit this kind of access
Launches a nuclear missile from a specified silo to target coordinates. IMPORTANT: Check the response to verify if launch was successful!. It is categorised as a Execute tool in the Defcon MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Defcon MCP server in PolicyLayer and add a rule for launch-nuke: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Defcon. Nothing to install.
launch-nuke 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 launch-nuke rule in your PolicyLayer 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 PolicyLayer policy for launch-nuke. 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.
launch-nuke is provided by the Defcon MCP server (jorisvddonk/defcon-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →