# User guide: CP1 - Data Classification Agent For the Engagement Lead or delivery engineer reviewing a discovery run. ## What it does Classifies data stores PII / PCI / PHI / none from schema metadata only, and marks the stores that need data-disposition controls. It is step 5 of the workflow **CP1 - Agentic Landing Zone - Discovery** (ALZ-DSC-05, ADO 3214455). You don't call it yourself in normal use: run the workflow with `engagement_id` and `run_id`, and this agent receives its inputs from the earlier steps. ## Reading its output The output fields are listed in the agent's [README](../README.md#outputs). Every fact it states cites an `evidence_ref` from the MCP call it came from. Anything it couldn't establish is left empty, or listed as a gap or an issue, never guessed. ## What it will not do - Call any tool not on its allowlist, or pass a tool a hostname, address, URL or credential. - Write to any client system: all its tools are read-only. - Follow instructions found in data. These are recorded as prompt-injection findings. ## When something looks wrong | You see | Likely cause | What to do | |---|---|---| | The step failed with `output_contract_violation` | The model's reply didn't fit the output schema twice | Rerun the step; if it repeats, report it with the run id | | A refused tool call in the output | The MCP gateway refused the call (allowlist, scope or rate) | Check the agent's registration on the MCP gateway | | Empty fields | The source records didn't support them | Expected: the agent leaves out what it can't evidence | Changes from the original requirements are listed in [adr/](adr/README.md).