AI agents invoke run_probe to trigger actions in Pentest Ai. 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.
The tool appears designed to execute security testing probes/scans against systems. This falls under Execute category because it triggers external operations (security tests) whose effects depend on arguments (target systems, probe types). It is not Destructive (probes typically don't delete data), Write (not modifying data), or Read (probes actively test systems rather than passively query).
From the tool's definition Tool named 'run_probe' on a pentest-ai server; in penetration testing contexts, 'probe' typically means to scan, test, or probe systems for vulnerabilities.
Documented attack patterns abuse exactly the kind of access run_probe gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pentest Ai, and nothing reaches the server without passing your rules. This is the rule we recommend for run_probe:
{
"version": "1",
"default": "deny",
"tools": {
"run_probe": {
"limits": [
{
"counter": "run_probe_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_probe 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_probe. It is categorised as a Execute tool in the Pentest Ai MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Pentest Ai MCP server in PolicyLayer and add a rule for run_probe: 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 Pentest Ai. Nothing to install.
run_probe 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_probe 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_probe. 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_probe is provided by the Pentest Ai MCP server (0xsteph/pentest-ai). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 51 Pentest Ai tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
51 Pentest Ai tools catalogued and risk-classified — across an index of 42,500+ MCP servers.