docker_restart_container · HomeOps MCP Server MCP

WHAT IT DOES

What docker_restart_container does on HomeOps MCP Server

AI agents invoke docker_restart_container to trigger actions in HomeOps 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.

WHY IT NEEDS A POLICY

Why docker_restart_container needs a policy

This tool executes a command against external infrastructure (Docker) that causes a state change in running services. While not destructive (the container itself persists), and not a direct read or write of data, it triggers an external operation whose real-world impact depends on the argument provided. An agent with misuse access could disrupt critical home services (media server, home automation, etc.).

From the tool's definition Tool name is 'docker_restart_container' and description states it will 'Restart a Docker container by name.' Restarting a container is an operational action that triggers external effects (stopping and restarting a running service), whose consequences depend…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

docker_restart_container Rate-limited

docker_restart_container stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "docker_restart_container": {
      "limits": [
        {
          "counter": "docker_restart_container_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches HomeOps MCP Server, so you can run agents against it safely.

FAQ

Questions about docker_restart_container

What does the docker_restart_container tool do? +

Restart a Docker container by name. It is categorised as a Execute tool in the HomeOps MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on docker_restart_container? +

Register the HomeOps MCP Server MCP server in PolicyLayer and add a rule for docker_restart_container: 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 HomeOps MCP Server. Nothing to install.

What risk level is docker_restart_container? +

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

Can I rate-limit docker_restart_container? +

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

How do I block docker_restart_container completely? +

Set action: deny in the PolicyLayer policy for docker_restart_container. 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 docker_restart_container? +

docker_restart_container is provided by the HomeOps MCP Server MCP server (wolffcatskyy/homeops-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.