run_container

Run Docker container

SERVERNcp SOURCE@portel/ncp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-portel-dev-ncp/run-container.md

WHAT IT DOES

What run_container does on Ncp

AI agents invoke run_container to trigger actions in Ncp. 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.

RISK

Why run_container is rated High

This tool executes arbitrary containerized workloads. The blast radius is high because a malicious prompt could run any Docker container with any configuration, potentially accessing sensitive mounts, exfiltrating data, consuming resources, or pivoting to other systems.

From the tool's definition Tool name 'run_container' combined with description 'Run Docker container' indicates execution of containerized code/operations with externally-determined effects based on arguments (which container, what commands, what mounts, etc.).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs run_container safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_container, this is the rule to start with:

run_container Rate-limited

run_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": {
    "run_container": {
      "limits": [
        {
          "counter": "run_container_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 Ncp, apply this rule, and every run_container call is checked against it from then on.

FAQ

Questions about run_container

What does the run_container tool do? +

Run Docker container. It is categorised as a Execute tool in the Ncp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_container? +

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

What risk level is run_container? +

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

Can I rate-limit run_container? +

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

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

run_container is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ncp, and thousands of servers like it.

This server

All 275 Ncp tools → High-risk tools on this server →

Across the catalogue

shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

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