> ## Documentation Index > Fetch the complete documentation index at: https://docs.quintai.dev/llms.txt > Use this file to discover all available pages before exploring further. # Investigate a finding > From a finding on the Findings page to the session, the machine and a decision, in one pass. A finding is one place where what an agent declared it would do and what the machine saw it do came apart. The **Findings** page lists them; this is the path from a row to a decision. Setting a verdict needs the Policy Writer role or higher. **1. Pick the finding** Open **Findings**. Filter by severity (**critical**, **high**, **medium**, **low**), by family (**intent vs truth**, **supply chain**) and by verdict (**Unjudged** is where new work is). In the **Findings** panel choose **Flat** and sort **By severity** to work from the top. Each row shows **Severity**, **Finding** (name and type id), **What happened**, **Score**, **Verdict**, **Session** and **Age**. **2. Read what was declared and what was observed** Open the row. The **Overview** tab pairs the declared action with the observed one; the **Evidence** tab shows **Detector evidence**: the recorded facts the finding rests on. **Raw** shows the same as data. **Framework mappings** names the controls this type of finding maps to. The page says it plainly: "it is not a compliance opinion." **3. Follow it into the session** Use **Open session** or **View in timeline**. The session page shows the **Activity timeline** of every action in order, **Session info** (working directory, agent, platform, model, parent session), **Child sessions** the agent spawned, and **Process lineage**. Look at what happened just before and after the finding. **4. Check the machine** From the session, open the host. The host page shows its capture layers, heartbeat, install integrity and the agents on it. A host marked **Degraded** or with a note that "lane states are last-known readings" may be missing evidence, which changes how much weight the finding carries. **5. Ask Sentinel if the picture is unclear** **Investigate in Sentinel** opens a conversation seeded with the finding. Sentinel answers from your workspace's own rows and shows every query it ran. See [Ask Sentinel](https://docs.quintai.dev/dashboard/sentinel.md). **6. Record a verdict** Back on the finding, set **True positive**, **False positive** or **Suspicious**. Verdicts are filters on the list, so an unjudged queue stays short. **Export CSV** exports the current list. **7. Track it, or prevent it** Only a critical alert opens an **Incident** on its own. For anything else you want tracked to resolution, open **Incidents** and work the record. The panel beside it has three menus: **Status** (**Open**, **Investigating**, **Resolved**; an older record may show **Contained** or **Closed**), **Owner** and **Verdict**. The button at the top offers the next step: **Assign to me** while nobody owns the record, then **Set verdict**. The **⋯** menu holds **Copy link**, **Copy id**, **Open the first session** and **Status…**. Add a note under **History** with **Add note**. Assigning to another person needs Admin or Owner. The panel's **Response** card has **Draft a shadow rule**, which opens **Policies › Rules**, where you draft the rule. See [Write and publish a rule](https://docs.quintai.dev/policies/write-and-publish-a-rule.md). ## What the risk names mean | Category | Finding names | | - | - | | Credential access | Credential read; Credential store modified | | Exfiltration | Credential read, then egress | | Persistence | Persistence implant | | Execution | Undeclared command; Undeclared subprocess activity; Command differs from declared | | Unexpected change | Undeclared file write; Declared path deleted | | Intent mismatch | Read-only tool wrote a file; Path differs from declared; Action differs from declared | | Approval bypass | Agent approved its own action; Agent-steered approval | | Tool supply chain | MCP tool redefined; Tool description injection; Built-in tool changed; Tool cross-reference | Anything outside this list appears as "Other findings". On macOS, in an upcoming agent release, **Command differs from declared** judges the program that ran (under a declared `ls`, a shell starting `curl` is reported; a test runner starting `git` is not), and **Undeclared command** names that program. ## Tool supply-chain findings First-time checks, invisible characters and cross-references arrive in an upcoming agent release. Not checked: tools in OpenAI Chat, Bedrock Converse or Gemini formats; text inside a parameter schema. | Finding | What it means | Severity | Next step | | - | - | - | - | | **Tool description injection** | A third-party MCP tool's description carries instructions aimed at the model. Checked on a change and, from that release, when Quint first sees the tool; invisible characters the model can read are flagged too. From that release, a provider's routine rewording of a built-in tool is usually not flagged; today it can be. | **Medium** the first time, **high** on a change. | Read the recorded excerpt on the finding's **Evidence** tab. If you don't trust it, remove the server or pin a reviewed version. | | **Tool cross-reference** | One MCP server's tool description names a tool from a different MCP server offered at the same time. It matches names only: a lead, not proof. | **Low**. | Check you installed and expect both servers; remove any you don't. | ## If the list is empty "No divergences in this window." is a result for the window you chose. A note that counts are unavailable is not: it is a coverage gap, not a quiet fleet. Widen the window, then check **Coverage** on the Overview and the **Silent** filter on **Data Sources** before concluding the fleet was quiet. ## Next * [Decide an approval](https://docs.quintai.dev/dashboard/decide-an-approval.md) when a finding comes from a workload with approvals. * [Shadow enforcement](https://docs.quintai.dev/policies/shadow-enforcement.md) to see what a rule would have done about it. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.