start_wp_shell

Open an interactive PHP shell (REPL) within the context of the WordPress environment.

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/start-wp-shell.md

WHAT IT DOES

What start_wp_shell does on Pentester-MCP

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

This tool directly executes arbitrary PHP code within a live WordPress application. While framed as a penetration testing utility, providing an interactive shell that runs code in the target's context is the definition of Execute capability. The ability to run arbitrary commands in a WordPress environment gives an AI agent unrestricted control over the target system, making this critical severity.

From the tool's definition Opens an interactive PHP shell (REPL) within WordPress context—enables arbitrary code execution in the target application environment.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

start_wp_shell Rate-limited

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

FAQ

Questions about start_wp_shell

What does the start_wp_shell tool do? +

Open an interactive PHP shell (REPL) within the context of the WordPress environment. 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 start_wp_shell? +

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

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

Can I rate-limit start_wp_shell? +

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

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

start_wp_shell 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

start_devtools_monitoring on Percepta MCP Server →adb_shell_command on Android Forensics ADB MCP Server →team_manager_start_room on Team Manager MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

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