Context quarantine and roles

This workflow covers client scope intake, model-driven Pentest MCP execution, durable evidence, report drafting, analyst verification and final publication. Pentest MCP provides the value: a model session without successful MCP assessment records is rejected.

Keep the concrete client environment inventory and authorization record in private engagement storage outside the public distribution and outside the assessor's builder context.

Roles and quarantine

Role	Input	Output	Quarantine rule
Scope author	Client authorization, assets, windows, methods, data rules	Engagement and assessment plan	Never enters assessor or report transcript
Assessment agent	One scope, one plan, MCP catalog	Tool calls, evidence, coverage and unverified observations	Fresh CLI home/work directory or guarded API loop; no builder repo, scope chat or other engagement
Report agent	Bounded scope/plan and evidence packet	Evidence-cited analyst draft	Separate process/home; no assessment MCP or assessor transcript
Analyst reviewer	Draft and cited source records	Verified findings and approved language	Model candidates have no publication authority

The owner boundary isolates engagements across authenticated HTTP principals and local stdio installations. Human role separation still requires separate accounts or operating procedures. Attribution fields are not digital signatures.