n0s1-mcp

get_scan_findings

Read-only

Retrieve paginated findings from a completed secret scan, filtered by severity, with secret values redacted. Use next_cursor to navigate pages without exposing raw secrets.

Instructions

Return a paginated list of findings for a completed scan. Read-only with no side effects. All secret values are redacted — raw secrets are never returned. Pass next_cursor from a previous response to retrieve subsequent pages.

Input Schema

TableJSON Schema

Name	Required	Description
`report_uuid`	Yes	UUID returned by the originating scan_* call
`page`	No	Opaque cursor from a previous response (omit for first page)
`severity`	No	Filter findings to this severity level

Output Schema

TableJSON Schema

Name	Required	Description	Default
`report_uuid`	Yes
`findings`	Yes
`next_cursor`	No
`total`	Yes
`usage`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.1.4Jun 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "Finding": {
+      "description": "A single redacted secret finding.",
+      "properties": {
+        "file": {
+          "title": "File",
+          "type": "string"
+        },
+        "line": {
+          "anyOf": [
+            {
+              "type": "integer"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "title": "Line"
+        },
+        "redacted_match": {
+          "title": "Redacted Match",
+          "type": "string"
+        },
+        "severity": {
+          "$ref": "#/$defs/Severity"
+        },
+        "type": {
+          "title": "Type",
+          "type": "string"
+        }
+      },
+      "required": [
+        "file",
+        "type",
+        "severity",
+        "redacted_match"
+      ],
+      "title": "Finding",
+      "type": "object"
+    },
+    "Severity": {
+      "enum": [
+        "info",
+        "low",
+        "medium",
+        "high",
+        "critical"
+      ],
+      "title": "Severity",
+      "type": "string"
+    },
+    "Usage": {
+      "description": "Token-usage accounting block.",
+      "properties": {
+        "savings_pct": {
+          "title": "Savings Pct",
+          "type": "number"
+        },
+        "tokens_in_estimate": {
+          "title": "Tokens In Estimate",
+          "type": "integer"
+        },
+        "tokens_out_actual": {
+          "title": "Tokens Out Actual",
+          "type": "integer"
+        },
+        "tokens_saved_estimate": {
+          "title": "Tokens Saved Estimate",
+          "type": "integer"
+        }
+      },
+      "required": [
+        "tokens_in_estimate",
+        "tokens_out_actual",
+        "tokens_saved_estimate",
+        "savings_pct"
+      ],
+      "title": "Usage",
+      "type": "object"
+    }
+  },
+  "description": "Paginated findings list for an existing scan.",
+  "properties": {
+    "findings": {
+      "items": {
+        "$ref": "#/$defs/Finding"
+      },
+      "title": "Findings",
+      "type": "array"
+    },
+    "next_cursor": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Next Cursor"
+    },
+    "report_uuid": {
+      "title": "Report Uuid",
+      "type": "string"
+    },
+    "total": {
+      "title": "Total",
+      "type": "integer"
+    },
+    "usage": {
+      "$ref": "#/$defs/Usage"
+    }
+  },
+  "required": [
+    "report_uuid",
+    "findings",
+    "total",
+    "usage"
+  ],
+  "title": "FindingsPage",
+  "type": "object"
+}

First observedv1.1.1Jun 9, 2026

TDQS

A4.4/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Description reinforces the readOnlyHint annotation with 'Read-only with no side effects' and adds critical info about secret redaction and pagination behavior, which annotations do not cover.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three lean sentences: purpose, side effects, and key behavioral detail (redaction + pagination). Every sentence adds value without waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, read-only guarantee, redaction, and pagination. Could mention what happens if scan is not completed, but output schema likely handles error cases. Largely complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so parameters are well-defined in the schema. Description only paraphrases the pagination cursor behavior, adding no new semantic meaning beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the tool returns a paginated list of findings for a completed scan, using a specific verb and resource. The name and context distinguish it from sibling tools that initiate scans or check status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies the tool is for completed scans and mentions pagination with next_cursor, but does not explicitly compare to sibling tools like analyze_report or state when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server