// MCP TOOL REFERENCE

arcane_system_containers_stop_all

[HIGH RISK] Stop ALL running containers in an environment

Bulk/mass operation — affects multiple targets

Part of the Arcane MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@randomsynergy/arcane-mcp-server Execute

// WHEN AI AGENTS USE THIS TOOL

AI agents invoke arcane_system_containers_stop_all to trigger processes or run actions in Arcane. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

// WHY ENFORCE A POLICY ON ARCANE_SYSTEM_CONTAINERS_STOP_ALL

arcane_system_containers_stop_all can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

// RECOMMENDED POLICY

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

arcane.yaml

tools:
  arcane_system_containers_stop_all:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Arcane policy for all 180 tools.

// DETAILS

Tool Name arcane_system_containers_stop_all

Category Execute

MCP Server Arcane MCP Server

Risk Level High

// MORE ARCANE TOOLS

Destructive arcane_apikey_delete Destructive arcane_container_delete Destructive arcane_environment_delete Destructive arcane_event_delete Destructive arcane_git_repo_delete Destructive arcane_gitops_delete Destructive arcane_image_delete Destructive arcane_image_prune

View all 180 tools →

// WHAT CAN GO WRONG

Agents calling execute-class tools like arcane_system_containers_stop_all have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER EXECUTE TOOLS ACROSS MCP SERVERS

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

Agent Passport System — Cryptographic Identity for AI Agents aps_aggregate_settlement Agent Passport System — Cryptographic Identity for AI Agents aps_build_contributor_query Agent Passport System — Cryptographic Identity for AI Agents aps_compute_compute_axis_weights Agent Passport System — Cryptographic Identity for AI Agents aps_construct_attribution_primitive Agent Passport System — Cryptographic Identity for AI Agents commerce_preflight Agent Passport System — Cryptographic Identity for AI Agents execute_with_context

// IN CONTEXT OF HIGH RISK

arcane_system_containers_stop_all is one of the high-risk operations in Arcane. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

// RELATED READING

// FAQ

What does the arcane_system_containers_stop_all tool do? +

[HIGH RISK] Stop ALL running containers in an environment. It is categorised as a Execute tool in the Arcane MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on arcane_system_containers_stop_all? +

Add a rule in your Intercept YAML policy under the tools section for arcane_system_containers_stop_all. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Arcane MCP server.

What risk level is arcane_system_containers_stop_all? +

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

Can I rate-limit arcane_system_containers_stop_all? +

Yes. Add a rate_limit block to the arcane_system_containers_stop_all rule in your Intercept 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 arcane_system_containers_stop_all completely? +

Set action: deny in the Intercept policy for arcane_system_containers_stop_all. 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 arcane_system_containers_stop_all? +

arcane_system_containers_stop_all is provided by the Arcane MCP server (@randomsynergy/arcane-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

arcane_system_containers_stop_all

Let agents act without letting them run wild.