inspect_container · MCP Developer Server MCP: Risk & Policy

WHAT IT DOES

What inspect_container does on MCP Developer Server

AI agents invoke inspect_container to trigger actions in MCP Developer Server. 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 inspect_container needs a policy

The tool both inspects a container (Read) and executes docker commands (Execute). Per the severity hierarchy, Execute outranks Read. Running arbitrary docker commands can have significant side effects depending on the command — e.g., modifying container state, networking, volumes — making the blast radius high if misused by an AI agent.

From the tool's definition 'Inspects the container, and runs the command docker command' — explicitly runs a docker command inside/against a container

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

inspect_container Rate-limited

inspect_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": {
    "inspect_container": {
      "limits": [
        {
          "counter": "inspect_container_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 MCP Developer Server, so you can run agents against it safely.

FAQ

Questions about inspect_container

What does the inspect_container tool do? +

Inspects the container, and runs the command docker command. It is categorised as a Execute tool in the MCP Developer Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on inspect_container? +

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

What risk level is inspect_container? +

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

Can I rate-limit inspect_container? +

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

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

inspect_container is provided by the MCP Developer Server MCP server (ra86-dev/mcpdev-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.