run_probe

A execute tool on the Pentest Ai MCP server.

SERVERPentest Ai SOURCE0xsteph/pentest-ai

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/0xsteph-pentest-ai/run-probe.md

WHAT IT DOES

What run_probe does on Pentest Ai

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.

RISK

Why run_probe is rated High

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs run_probe safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Pentest Ai, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_probe, this is the rule to start with:

run_probe Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_probe": {
      "limits": [
        {
          "counter": "run_probe_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 Pentest Ai, apply this rule, and every run_probe call is checked against it from then on.

FAQ

Questions about run_probe

What does the run_probe tool do? +

run_probe is a execute tool on the Pentest Ai MCP server. 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.

How do I enforce a policy on run_probe? +

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.

What risk level is run_probe? +

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

Can I rate-limit run_probe? +

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.

How do I block run_probe completely? +

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.

What MCP server provides run_probe? +

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.

KEEP EXPLORING

More on Pentest Ai, and thousands of servers like it.

This server

All 51 Pentest Ai tools → High-risk tools on this server →

Across the catalogue

shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

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