system_stop_container

A execute tool on the Hercules MCP server.

SERVERHercules MCP SOURCE0xmihirk/hercules-mcp
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/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

Questions about system_stop_container

What does the system_stop_container tool do? +

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.

How do I enforce a policy on system_stop_container? +

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.

What risk level is system_stop_container? +

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

Can I rate-limit system_stop_container? +

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.

How do I block system_stop_container completely? +

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.

What MCP server provides system_stop_container? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Hercules's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.