AI agents invoke container_start to trigger actions in ChatGPT MCP 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.
Starting a container executes arbitrary code or services defined within that container. While not immediately destructive, the action initiates processes whose side effects are determined by the container's configuration and cannot be precisely predicted without inspecting the image.
From the tool's definition Tool name is 'container_start' and description states 'Start a stopped container'. This triggers external operations (Docker container execution) whose effects depend on the container's configured behavior and entrypoints.
Documented attack patterns abuse exactly the kind of access container_start gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ChatGPT MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for container_start:
{
"version": "1",
"default": "deny",
"tools": {
"container_start": {
"limits": [
{
"counter": "container_start_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}container_start 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.
Free to start. No card required.
Start a stopped container. It is categorised as a Execute tool in the ChatGPT MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ChatGPT MCP Server MCP server in PolicyLayer and add a rule for container_start: 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 ChatGPT MCP Server. Nothing to install.
container_start 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 container_start 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 container_start. 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.
container_start is provided by the ChatGPT MCP Server MCP server (toowiredd/chatgpt-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ChatGPT MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 ChatGPT MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.