controld-mcp

Temporarily pause Control D

pause_profile

Destructive

Temporarily stop all DNS enforcement on a selected profile for a set number of minutes, with explicit confirmation required before live changes take effect.

Instructions

Pause all enforcement on a profile for a bounded time. This changes live DNS behavior and requires confirm=true.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "profile": "<profile>",
      "minutes": "<minutes>",
      "confirm": "<confirm>"
    },
    "name": "pause_profile"
  }
}

Input Schema

Name	Required	Description
`confirm`	Yes	Must be exactly true after reviewing the requested change
`minutes`	Yes
`profile`	Yes	Exact profile name or profile ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 20, 2026

TDQS

A4.4/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds behavioral details beyond annotations, such as the impact on live DNS and the confirmation requirement. This enhances transparency about the tool's effects and prerequisites, complementing the destructiveHint annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, with two sentences: the first states the core purpose, and the second adds critical constraints. It is front-loaded and efficient, with no unnecessary fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description provides enough context for a destructive, non-idempotent action, including the need for confirmation and the live impact. It lacks details on return values or reversibility, but the absence of an output schema and the presence of a resume tool make it adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has partial descriptions for confirm and profile, but the minutes parameter lacks a description. The tool description mentions 'bounded time' but does not explicitly link it to the minutes parameter, so it only partially compensates for the missing schema description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool pauses all enforcement on a profile for a bounded time, which is specific and distinct from sibling tools like resume_profile. It effectively communicates the primary action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description mentions it changes live DNS behavior and requires confirm=true, giving usage context. It implies this is a temporary pause but does not explicitly contrast with resume_profile or other alternatives, though the name and sibling list make it clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server