docker_stop

Stop a running container.

SERVERYaver SOURCEyaver-cli

High RISK CLASS

Category Execute

Parameters 11 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/docker-stop.md

WHAT IT DOES

What docker_stop does on Yaver

AI agents invoke docker_stop 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.

RISK

Why docker_stop is rated High

Stopping a running container is an Execute action—it triggers an external operation (Docker daemon) with side effects dependent on which container is targeted. While reversible (containers can be restarted), this action immediately halts services and can disrupt deployments, applications, and workflows.

From the tool's definition Tool name 'docker_stop' and description 'Stop a running container' indicate execution of a container management command with immediate operational effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs docker_stop 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_stop, this is the rule to start with:

docker_stop Rate-limited

docker_stop 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_stop": {
      "limits": [
        {
          "counter": "docker_stop_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every docker_stop call is checked against it from then on.

FAQ

Questions about docker_stop

What does the docker_stop tool do? +

Stop a running 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.

What parameters does docker_stop accept? +

docker_stop accepts 1 parameter: container. Required: container. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on docker_stop? +

Register the Yaver MCP server in PolicyLayer and add a rule for docker_stop: 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.

What risk level is docker_stop? +

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

Can I rate-limit docker_stop? +

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

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

docker_stop 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.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools → High-risk tools on this server →

Across the catalogue

stop_emba_scan on EMBA-MCP →stop_etw_trace on Procmon → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →