system_stop_container
A execute tool on the Hercules MCP server.
This record as markdown: /tools/0xmihirk-hercules-mcp/system-stop-container.md
What system_stop_container does on Hercules MCP
AI agents invoke system_stop_container to trigger actions in Hercules MCP. 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 system_stop_container is rated High
This tool triggers external operations (container lifecycle management) whose effects depend on implementation—stopping a container halts all running tools, processes, and services within it. While not destructive to persistent data, it is an Execute category action as it controls system state and operations.
From the tool's definition Tool name 'system_stop_container' indicates stopping/halting a containerized Kali Linux environment. Description is empty, but context shows this server exposes offensive security tools in a containerized environment.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs system_stop_container safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hercules MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For system_stop_container, this is the rule to start with:
system_stop_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Hercules MCP, apply this rule, and every system_stop_container call is checked against it from then on.
Questions about system_stop_container
system_stop_container is a execute tool on the Hercules MCP server. It is categorised as a Execute tool in the Hercules MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Hercules MCP server in PolicyLayer and add a rule for system_stop_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 Hercules MCP. Nothing to install.
system_stop_container 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 system_stop_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.
Set action: deny in the PolicyLayer policy for system_stop_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.
system_stop_container is provided by the Hercules MCP server (0xmihirk/hercules-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hercules, and thousands of servers like it.
Across the catalogue