This record as markdown: /tools/aapanel-mcp/docker-container-restart.md
What docker_container_restart does on Aapanel
AI agents invoke docker_container_restart to trigger actions in Aapanel. 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 docker_container_restart is rated High
Restarting a Docker container is an execution action that causes real-world operational changes—the container process terminates and restarts, potentially disrupting services. While the operation is reversible (unlike destructive actions), it modifies system state and can impact availability.
From the tool's definition Tool name 'docker_container_restart' and description 'Restart a Docker container' indicate execution of a container management operation that triggers external effects.
Attacks that exploit this kind of access
The rule that runs docker_container_restart safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aapanel, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For docker_container_restart, this is the rule to start with:
docker_container_restart 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Aapanel, apply this rule, and every docker_container_restart call is checked against it from then on.
Questions about docker_container_restart
Restart a Docker container. It is categorised as a Execute tool in the Aapanel MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Aapanel MCP server in PolicyLayer and add a rule for docker_container_restart: 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 Aapanel. Nothing to install.
docker_container_restart 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 docker_container_restart 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 docker_container_restart. 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.
docker_container_restart is provided by the Aapanel MCP server (nipunanirmal/aapanel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aapanel, and thousands of servers like it.
Across the catalogue