run_raise_child

THE RISK

High Risk

Why run_raise_child needs a policy

The tool description is empty, reducing confidence slightly, but the server context and sibling tools strongly indicate this executes external commands or processes. The naming pattern and server purpose classify this as Execute rather than Write, as penetration testing tools typically trigger external operations whose effects depend on attacker-supplied arguments.

From the tool's definition Tool is on Pentester-MCP server which 'enables AI assistants to autonomously execute over 200 open-source penetration testing tools' including 'web exploitation' and 'brute-forcing'; name 'run_raise_child' suggests executing or spawning a process; sibling…

Documented attack patterns abuse exactly the kind of access run_raise_child gives an agent:

POLICY

How to control run_raise_child

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_raise_child:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_raise_child": {
      "limits": [
        {
          "counter": "run_raise_child_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

run_raise_child 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.

Create a free account and register Pentester-MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Pentester-MCP tools

Execute dnscat_client dnscat_client Execute execute_weevely_module execute_weevely_module Execute identify_hash identify_hash Execute john_prepare john_prepare Execute launch_xsser_gui Launches the graphical user interface (GTK) for XSSer. Execute objection_explore objection_explore Execute run_403bypasser run_403bypasser Execute run_addcomputer run_addcomputer

All 337 Pentester-MCP tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

Govern code and CI agents → Branch allowlists, approval on merges, and rate caps on the build and pipeline tools agents trigger.
High-risk tools in Pentester-MCP → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →
PolicyLayer vs alternatives → How deterministic, per-call MCP policy compares with gateways, identity layers, and authorisation platforms.

FAQ

Questions about run_raise_child

What does the run_raise_child tool do? +

run_raise_child. 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 run_raise_child? +

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

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

Can I rate-limit run_raise_child? +

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

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

run_raise_child 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.

Enforce policy on every Pentester-MCP tool call.

Start from Pentester-MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →