updateFinding
Update ONE existing Mallory finding in place — its status, severity, confidence, title, summary, body, remediation, qualifier or asset_details. Use it when new information changes an already-filed finding: the problem was fixed, it turned out not to apply, a vulnerability proved reachable, corroborating intel changes how bad it is.
WRITES IMMEDIATELY to the caller's own organization's data, and the result is visible in the Mallory UI to everyone in that organization. There is no preview and no confirmation step — calling this tool IS the write. Only call it when the user has asked for the change.
uuid identifies the finding. Get it from listFindings or getFinding, or from a createFinding DUPLICATE outcome's
existing_finding_uuid. Never construct or guess one.ONE finding per call. To change status or severity across a SET of findings you can only describe ("dismiss all the unrotated-secret findings", "mark everything on foo/bar medium"), use bulkUpdateFindings — do NOT loop this tool over a selection.
The finding's identity — definition_slug, asset_type, asset_identifier — cannot be changed. A different problem, or the same problem on a different asset, is a new finding (createFinding).
body REPLACES the stored text rather than appending to it. To add to a finding, read the current text first with getFinding and send the combined text, or the prior detail is lost. There is no evidence field on update: new evidence goes into body as prose.
asset_uuid links the finding to a resolved asset of any class. Find a name (or part of one) with GET /v1/assets using where=display_name == "" or display_name.contains(""); this searches every class and needs no class or key type. For an identity key whose kind the user provides (serial number, ARN, repo URL, digest), use GET /v1/assets/by-identifier?type=&value=; type is the identity key type, not the asset class, and class is optional. Count distinct asset_uuid values across the complete result: while there is a next_cursor, read the next page with cursor and unchanged filters and sort. A truncated or incomplete lookup cannot produce a link; with zero or multiple matches, omit asset_uuid and never guess. null removes the link and omission keeps it. It does not change asset_type or asset_identifier. For a finding whose asset_type is "host" or "asset", the link is the identity and cannot change (INVALID); create a new finding instead. Link the returned canonical asset_uuid as /environment/{asset_uuid}.
qualifier is part of core's open-finding dedupe key, so changing it can collide with another open finding on the same asset (CONFLICT).
In user-facing status messages, use "fixed" and "mark as fixed" consistently.
ENUM VALUES ARE CASE-SENSITIVE AND EACH FIELD HAS ITS OWN SET. severity is UPPERCASE (CRITICAL, HIGH, MEDIUM, LOW, INFO). status is lowercase with exactly three values: open, fixed, dismissed — "resolved", "closed" and "assigned" are not statuses, and neither are the resolution reasons (false_positive, accepted_risk, not_applicable, duplicate, fixed_externally, other), which belong to a separate field this tool does not set. Use "fixed" when the problem was remediated and "dismissed" when it is accepted or not applicable. Setting status back to "open" is allowed but unusual — the product has no reopen button — so confirm the user really means to reopen the finding.
OUTCOMES: either ok:true with the updated finding, or ok:false with a code — NOT_FOUND (no such finding in this tenant: do not retry, re-read the uuid), ASSET_NOT_FOUND (asset_uuid is not an asset of this organization: resolve it again, never guess), CONFLICT (an open finding already occupies that identity), INVALID (a rejected field, or no fields to change), PLAN_LIMIT (findings are not included in this tenant's plan — the request was fine, nothing is broken, nothing was written: say so and do not retry).
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"uuid": "<uuid>"
},
"name": "updateFinding"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| body | No | The detail: what was found, how, and why it matters. Rendered as markdown. REPLACES the existing body — when adding to a finding (e.g. why it was escalated), read the current body first and send the combined text, or the prior detail is lost. | |
| uuid | Yes | UUID of the finding to update. Comes from a create outcome's existing_finding_uuid, or from GET /v1/findings. | |
| title | No | Asset-scoped headline. Omit unless it is genuinely wrong. | |
| status | No | Lifecycle state. 'fixed' when the underlying problem is fixed, 'dismissed' when it is accepted or not applicable. | |
| summary | No | One or two sentences: what is wrong. Rendered as markdown. | |
| severity | No | New severity for this instance, e.g. when reachability or corroborating intel changes how bad it is. Overrides the definition's default. | |
| qualifier | No | Discriminator when one asset has several instances of the same definition. Part of the dedupe key — changing it can collide with another open finding (409). | |
| asset_uuid | No | Link to a resolved tenant asset of any class, or send null to clear the link. Omit to keep it. Find names with GET /v1/assets using where=display_name == "<name>" or display_name.contains("<text>"). For a typed identity key use GET /v1/assets/by-identifier?type=<key type>&value=<value>; type is the identity key type, not the asset class; class is optional. Set only one distinct asset_uuid from a complete lookup. The asset pair does not change. Merged UUIDs link to the survivor; unknown or cross-tenant assets give ASSET_NOT_FOUND. For findings whose asset_type is 'host' or 'asset', the link is immutable (INVALID). | |
| confidence | No | ||
| remediation | No | Concrete steps to fix it, ideally a runnable command. Rendered as markdown. | |
| asset_details | No | Free-form structured context about the asset (region, account, owner, ...). Replaces the stored object. |