docker_container_action · RedisNexus MCP: Risk & Policy

WHAT IT DOES

What docker_container_action does on RedisNexus

AI agents invoke docker_container_action to trigger actions in RedisNexus. 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_container_action needs a policy

This tool executes lifecycle operations on Docker containers including destructive actions (kill, remove) and disruptive actions (stop, pause) in addition to read-only ones (inspect, top, stats).

From the tool's definition Perform actions on containers: start, stop, restart, pause, kill, remove, inspect, top, stats

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

docker_container_action Rate-limited

docker_container_action 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_container_action": {
      "limits": [
        {
          "counter": "docker_container_action_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 RedisNexus, so you can run agents against it safely.

FAQ

Questions about docker_container_action

What does the docker_container_action tool do? +

Perform actions on containers: start, stop, restart, pause, kill, remove, inspect, top, stats. It is categorised as a Execute tool in the RedisNexus 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_container_action? +

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

What risk level is docker_container_action? +

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

Can I rate-limit docker_container_action? +

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

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

docker_container_action is provided by the RedisNexus MCP server (rajkumar-madhu/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

docker_container_action is one line of RedisNexus's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →