AI agents invoke stop_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.
This tool executes a system-level command to terminate a background shell process used in web exploitation attacks. While termination might appear reversible in isolation, in a penetration testing context it terminates active exploit shells—a consequential operation that triggers external effects (process termination) dependent on the supplied PID argument.
From the tool's definition Tool name 'stop_wp_shell' and description 'Terminates a background wp shell process by PID' indicate termination of a wp (WordPress exploitation) shell process. The server context describes 'open-source penetration testing tools' including 'web exploitation'.
Documented attack patterns abuse exactly the kind of access stop_wp_shell gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pentester-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for stop_wp_shell:
{
"version": "1",
"default": "deny",
"tools": {
"stop_wp_shell": {
"limits": [
{
"counter": "stop_wp_shell_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}stop_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.
Free to start. No card required.
Terminates a background wp shell process by PID. 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.
Register the Pentester- MCP server in PolicyLayer and add a rule for stop_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.
stop_wp_shell is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the stop_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.
Set action: deny in the PolicyLayer policy for stop_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.
stop_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.
Start from Pentester-MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
337 Pentester-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.