execute_weevely_module

A execute tool on the Pentester- MCP server.

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/execute-weevely-module.md

WHAT IT DOES

What execute_weevely_module does on Pentester-MCP

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

This tool executes code/commands via a web shell module. Weevely modules run arbitrary PHP code on target web servers, making this an Execute category risk. Severity is critical because: (1) it can execute arbitrary commands on remote systems, (2) blast radius is unlimited depending on target permissions, (3) the server explicitly mentions Docker sandboxing for execution safety, implying high-risk operations, and…

From the tool's definition Tool name 'execute_weevely_module' combined with server description indicating execution of 'over 200 open-source penetration testing tools' with 'web exploitation' capabilities.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

execute_weevely_module Rate-limited

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

FAQ

Questions about execute_weevely_module

What does the execute_weevely_module tool do? +

execute_weevely_module is a execute tool on the Pentester MCP server. 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 execute_weevely_module? +

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

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

Can I rate-limit execute_weevely_module? +

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

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

execute_weevely_module 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

claude_execute on Claude Bridge →execute_test_case on Percepta MCP Server →intercept_module_function on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

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