docker_exec
Execute a command inside a running Docker container. Requires confirmed: true. Output capped at 512KB.
This record as markdown: /tools/7majesty-m-terminal-guardian-mcp/docker-exec.md
What docker_exec does on Terminal Guardian
AI agents invoke docker_exec to trigger actions in Terminal Guardian. 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 docker_exec is rated High
This tool allows running arbitrary commands within Docker containers, which can have wide-ranging side effects depending on what commands are executed. While the server claims to provide sandboxing and risk analysis, the tool itself performs command execution whose effects depend entirely on the arguments provided. This places it in the Execute category rather than Read or Write.
From the tool's definition Tool description states "Execute a command inside a running Docker container". The word "Execute" directly indicates code execution capability. Combined with the ability to run arbitrary commands in containers, this is a clear Execute-category tool.
Attacks that exploit this kind of access
The rule that runs docker_exec safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Terminal Guardian, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For docker_exec, this is the rule to start with:
docker_exec 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 Terminal Guardian, apply this rule, and every docker_exec call is checked against it from then on.
Questions about docker_exec
Execute a command inside a running Docker container. Requires confirmed: true. Output capped at 512KB. It is categorised as a Execute tool in the Terminal Guardian MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Terminal Guardian MCP server in PolicyLayer and add a rule for docker_exec: 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 Terminal Guardian. Nothing to install.
docker_exec 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_exec 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_exec. 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_exec is provided by the Terminal Guardian MCP server (7majesty-m/terminal-guardian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Terminal Guardian, and thousands of servers like it.
Across the catalogue