Run Pipeline
run_pipelineExecutes specified scan phases with scope enforcement and human approval, resuming from the last completed phase.
Instructions
[AGGRESSIVE — requires human approval] Run the engagement pipeline, gated, resumable, in-process.
phases restricts to a comma list ("probe,scan"); from_phase starts
at a named phase; exploit adds the exploit phase (still refused unless
the scope authorizes exploitation).
Each phase runs through its registered MCP tool — the full control-plane
chain applies per phase — and results land in pipeline-state.json +
the audit log. Finished phases are skipped on re-entry, so a dropped
session resumes where it stopped.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "run_pipeline"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| phases | No | ||
| target | No | ||
| exploit | No | ||
| from_phase | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||