AI agents invoke run_wpprobe_scan 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.
WPProbe is a reconnaissance and exploitation tool that probes WordPress installations for vulnerabilities. Executing such tools constitutes the Execute category—it triggers external operations (scans, probes) whose effects depend on the target argument. While it may retrieve data (Read), its primary purpose is active vulnerability testing and potential exploitation (Execute).
From the tool's definition Tool name 'run_wpprobe_scan' indicates execution of WPProbe (a WordPress vulnerability scanner). The server description states it 'autonomously execute[s] over 200 open-source penetration testing tools' including 'web exploitation'.
Documented attack patterns abuse exactly the kind of access run_wpprobe_scan 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 run_wpprobe_scan:
{
"version": "1",
"default": "deny",
"tools": {
"run_wpprobe_scan": {
"limits": [
{
"counter": "run_wpprobe_scan_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_wpprobe_scan 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.
run_wpprobe_scan. 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 run_wpprobe_scan: 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.
run_wpprobe_scan 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 run_wpprobe_scan 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 run_wpprobe_scan. 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.
run_wpprobe_scan 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.