This record as markdown: /tools/io-github-kivanccakmak-yaver/docker-restart.md
What docker_restart does on Yaver
AI agents invoke docker_restart to trigger actions in Yaver. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
container | string | Yes |
Parameters from the server's own tool schema.
Why docker_restart is rated High
This tool executes a command that restarts a Docker container—a real-world operation with immediate side effects on running services. While not destructive (the container itself is not deleted), it is an Execute action because it triggers an external operation (container restart) with effects that depend on runtime arguments (which container).
From the tool's definition Tool name 'docker_restart' and description 'Restart a container' indicate execution of a container management operation.
Attacks that exploit this kind of access
The rule that runs docker_restart safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For docker_restart, this is the rule to start with:
docker_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 Yaver, apply this rule, and every docker_restart call is checked against it from then on.
Questions about docker_restart
Restart a container. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
docker_restart accepts 1 parameter: container. Required: container. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for docker_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 Yaver. Nothing to install.
docker_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_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_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_restart is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
Across the catalogue