stop_commix_session

Terminates a background Commix session (pseudo-shell or reverse shell handler)

SERVERPentester-MCP SOURCEhalilkirazkaya/pentester-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/halilkirazkaya-pentester-mcp/stop-commix-session.md

WHAT IT DOES

What stop_commix_session does on Pentester-MCP

AI agents invoke stop_commix_session to trigger actions in Pentester-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.

RISK

Why stop_commix_session is rated High

This tool triggers termination of an active exploitation session (pseudo-shell or reverse shell), which is an external operation with side effects on a live target system. While the action itself is 'stopping' rather than 'starting', it represents control over an active Execute primitive (shell handler).

From the tool's definition Tool terminates a background Commix session, including pseudo-shell or reverse shell handler. Commix is a command injection exploitation framework that establishes interactive shell access to target systems.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs stop_commix_session safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Pentester-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stop_commix_session, this is the rule to start with:

stop_commix_session Rate-limited

stop_commix_session 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "stop_commix_session": {
      "limits": [
        {
          "counter": "stop_commix_session_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Pentester-MCP, apply this rule, and every stop_commix_session call is checked against it from then on.

FAQ

Questions about stop_commix_session

What does the stop_commix_session tool do? +

Terminates a background Commix session (pseudo-shell or reverse shell handler). It is categorised as a Execute tool in the Pentester-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 stop_commix_session? +

Register the Pentester MCP server in PolicyLayer and add a rule for stop_commix_session: 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 Pentester-MCP. Nothing to install.

What risk level is stop_commix_session? +

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

Can I rate-limit stop_commix_session? +

Yes. Add a rate_limit block to the stop_commix_session 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 stop_commix_session completely? +

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

stop_commix_session is provided by the Pentester MCP server (halilkirazkaya/pentester-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Pentester, and thousands of servers like it.

This server

All 337 Pentester tools → High-risk tools on this server →

Across the catalogue

stop_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →