mcp-autopentest-orchestrator
Installation
SKILL.md
MCP Autopentest Orchestrator
Semi-autonomous driver for the kit. Read ../../SECURITY_RULES.md first — it overrides everything here.
Autonomy boundary (non-negotiable):
- Read-only by default. The deterministic runner never calls write/destructive tools authenticated; the orchestrator must not either. Writes = human gate.
- Scope-lock: one authorized host, taken from
policy.json. Never probe a host not in scope (no SSRF-out, no prod-by-accident). - Rate-limit per policy. This is assessment, not load testing.
- Redact secrets: type + location + first4/last4 only.
- Show the plan before any live probe. Stop and ask when a write/destructive test is the only way forward.
Inputs
../../autonomy/policy.json(frompolicy.example.json): target, scope_lock_host, your own short-lived token, tenant/project headers, rate limit.