mcp

Mcp Mark Code Scan Finding Treated

Record that a hardcoded string became a key (mcp:*).

MCP twin of POST /v1/projects/{id}/code-scan/findings/{id}/treated. The finding id goes in the BODY here rather than the path, so the tool schema stays one flat object like the other MCP writes.

IDEMPOTENT: re-marking the same finding with the same key returns the row unchanged and does NOT move treated_at. An unknown finding_id is a 404 — it never silently creates a finding, so a typo cannot invent a treated record that no scan ever reported.

post/v1/mcp/projects/{project_id}/code-scan/findings/treated

Request

  • Base URL: https://api.sonenta.dev
  • URL: https://api.sonenta.dev/v1/mcp/projects/{project_id}/code-scan/findings/treated
  • Auth: none declared

Path parameters

project_idstring required

Request body

finding_idstring required

uuid of the finding (from list_code_scan_findings).

keystring required

The key NAME this hardcoded string became.

namespacestring nullable

Namespace slug of the key. Send it (with the key you just created) so the backend verifies the key EXISTS before marking treated — a treated finding then points at a real key. Omitting it keeps the legacy unchecked behaviour.

Response

Successful Response

object required

Changes

No recorded changes to this operation across all 1 revision of this API.