# docker-restart

Restart Docker containers with optional timeout

Agent View of the PolicyLayer registry record for `docker-restart`. HTML page: https://policylayer.com/tools/0xshariq-docker-mcp-server/docker-restart

## Facts

- Tool: `docker-restart`
- Server: Docker MCP Server (`0xshariq/docker-mcp-server`) — https://policylayer.com/tools/0xshariq-docker-mcp-server.md
- Homepage: https://github.com/0xshariq/docker-mcp-server
- Risk category: Execute (High risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "docker-restart",
    "arguments": {}
  }
}
```

## Why docker-restart is rated High

This tool executes container lifecycle operations with side effects that cannot be rolled back once the restart completes. While not destructive (data persists if properly configured) or financial, it directly triggers external system state changes. The blast radius is high: restarting a production database container could cause downtime, restart loops, or loss of in-memory state.

From the tool's own definition: "'Restart Docker containers' - this triggers external operations (container restart) whose effects depend on arguments (which containers, timeout settings)."

## Use case

AI agents invoke docker-restart to trigger actions in Docker MCP Server. 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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Docker MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "docker-restart": {
      "limits": [
        {
          "counter": "docker-restart_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Docker MCP Server (23)

- `docker-clean` — Destructive — https://policylayer.com/tools/0xshariq-docker-mcp-server/docker-clean.md
- `docker-prune` — Destructive — https://policylayer.com/tools/0xshariq-docker-mcp-server/docker-prune.md
- `docker-remove` — Destructive — https://policylayer.com/tools/0xshariq-docker-mcp-server/docker-remove.md
- `docker-reset` — Destructive — https://policylayer.com/tools/0xshariq-docker-mcp-server/docker-reset.md
- `docker-build` — Execute — https://policylayer.com/tools/0xshariq-docker-mcp-server/docker-build.md
- `docker-compose` — Execute — https://policylayer.com/tools/0xshariq-docker-mcp-server/docker-compose.md
- `docker-dev` — Execute — https://policylayer.com/tools/0xshariq-docker-mcp-server/docker-dev.md
- `docker-exec` — Execute — https://policylayer.com/tools/0xshariq-docker-mcp-server/docker-exec.md
- `docker-login` — Execute — https://policylayer.com/tools/0xshariq-docker-mcp-server/docker-login.md
- `docker-logout` — Execute — https://policylayer.com/tools/0xshariq-docker-mcp-server/docker-logout.md
- `docker-publish` — Execute — https://policylayer.com/tools/0xshariq-docker-mcp-server/docker-publish.md
- `docker-run` — Execute — https://policylayer.com/tools/0xshariq-docker-mcp-server/docker-run.md
- `docker-start` — Execute — https://policylayer.com/tools/0xshariq-docker-mcp-server/docker-start.md
- `docker-stop` — Execute — https://policylayer.com/tools/0xshariq-docker-mcp-server/docker-stop.md
- `docker-containers` — Read — https://policylayer.com/tools/0xshariq-docker-mcp-server/docker-containers.md
- `docker-images` — Read — https://policylayer.com/tools/0xshariq-docker-mcp-server/docker-images.md
- `docker-inspect` — Read — https://policylayer.com/tools/0xshariq-docker-mcp-server/docker-inspect.md
- `docker-list` — Read — https://policylayer.com/tools/0xshariq-docker-mcp-server/docker-list.md
- `docker-logs` — Read — https://policylayer.com/tools/0xshariq-docker-mcp-server/docker-logs.md
- `docker-bridge` — Write — https://policylayer.com/tools/0xshariq-docker-mcp-server/docker-bridge.md
- `docker-network` — Write — https://policylayer.com/tools/0xshariq-docker-mcp-server/docker-network.md
- `docker-pull` — Write — https://policylayer.com/tools/0xshariq-docker-mcp-server/docker-pull.md
- `docker-volume` — Write — https://policylayer.com/tools/0xshariq-docker-mcp-server/docker-volume.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=0xshariq-docker-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0xshariq-docker-mcp-server