stop_weevely_session

Terminates a background Weevely session.

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-weevely-session.md

WHAT IT DOES

What stop_weevely_session does on Pentester-MCP

AI agents invoke stop_weevely_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_weevely_session is rated High

This tool executes a termination command against a running Weevely session, which is a remote code execution shell. While the specific action is stopping rather than starting malicious activity, it still falls under Execute because it triggers an external operation whose effects depend on which session is targeted.

From the tool's definition Tool 'stop_weevely_session' terminates a Weevely session. Weevely is a web shell backdoor tool commonly used in penetration testing. The action of terminating a session is an external operation that affects an active remote process.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs stop_weevely_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_weevely_session, this is the rule to start with:

stop_weevely_session Rate-limited

stop_weevely_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_weevely_session": {
      "limits": [
        {
          "counter": "stop_weevely_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_weevely_session call is checked against it from then on.

FAQ

Questions about stop_weevely_session

What does the stop_weevely_session tool do? +

Terminates a background Weevely session. 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_weevely_session? +

Register the Pentester MCP server in PolicyLayer and add a rule for stop_weevely_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_weevely_session? +

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

Can I rate-limit stop_weevely_session? +

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

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

stop_weevely_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 →