restart_container · MCP Developer Server MCP: Risk & Policy

WHAT IT DOES

What restart_container does on MCP Developer Server

AI agents invoke restart_container to trigger actions in MCP Developer 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 restart_container needs a policy

Restarting a container is an operational action that executes a system command with side effects. While not destructive (data persists) or financial, it is an Execute category tool because it performs an action external to the MCP server itself. Severity is medium because misuse could disrupt development environments or services, but the effect is reversible and scoped to a single container.

From the tool's definition Tool name 'restart_container' and description 'Restart a container' indicate an action that triggers an external operation (container restart) whose effects depend on which container is targeted.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

restart_container Rate-limited

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": {
    "restart_container": {
      "limits": [
        {
          "counter": "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 MCP Developer Server, so you can run agents against it safely.

FAQ

Questions about restart_container

What does the restart_container tool do? +

Restart a container. It is categorised as a Execute tool in the MCP Developer 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 restart_container? +

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

What risk level is restart_container? +

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

Can I rate-limit restart_container? +

Yes. Add a rate_limit block to the 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 restart_container completely? +

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

restart_container is provided by the MCP Developer Server MCP server (ra86-dev/mcpdockershell). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.