@zivis/mcp 0.1.11 → 0.1.17

package/dist/tools/get-diagram.js

@@ -1,13 +1,9 @@
 import { z } from "zod";
 import { sanitizeResponse } from "../sanitize.js";
 export const GET_DIAGRAM_NAME = "zivis_get_diagram";
-export const GET_DIAGRAM_DESCRIPTION = `Get the full content of a diagram including all nodes, connections, boundaries, and Mermaid source.
+export const GET_DIAGRAM_DESCRIPTION = `Get the full content of a diagram, including its Mermaid source.
 
-Returns node IDs, names, tags, positions, boundary assignments, and metadata. Connection IDs include source/target node references and labels. Boundary IDs include labels and positions.
-
-For mermaid-type diagrams, the \`content\` field contains the full Mermaid source string — use it to read or render the diagram. For canvas-type diagrams, \`content\` is null and the structure is expressed via nodes/connections/boundaries.
-
-Use this before modifying a diagram — you need node/connection/boundary IDs for zivis_manage_diagram (canvas) or the Mermaid source for zivis_update_mermaid_source (mermaid).`;
+Use this before modifying a diagram — you need the current Mermaid source for zivis_update_mermaid_source.`;
 export const GET_DIAGRAM_SCHEMA = {
     diagram_id: z
         .string()
@@ -18,49 +14,6 @@ export function createGetDiagramHandler(apiClient) {
         try {
             const data = await apiClient.get(`/api/diagrams/${params.diagram_id}`);
             const sanitized = sanitizeResponse(data);
-            const nodes = Array.isArray(sanitized.nodes)
-                ? sanitized.nodes.map((n) => ({
-                    node_id: n.id,
-                    name: n.name,
-                    description: n.description || null,
-                    tags: n.tags || [],
-                    icon: n.icon || null,
-                    color: n.color || null,
-                    position_x: n.positionX,
-                    position_y: n.positionY,
-                    width: n.width,
-                    height: n.height,
-                    step_order: n.stepOrder || null,
-                    boundary_id: n.boundaryId || null,
-                    metadata: n.metadata || null,
-                    linked_finding_ids: n.linkedFindingIds || [],
-                    linked_evidence_ids: n.linkedEvidenceIds || [],
-                }))
-                : [];
-            const connections = Array.isArray(sanitized.connections)
-                ? sanitized.connections.map((c) => ({
-                    connection_id: c.id,
-                    source_node_id: c.sourceNodeId,
-                    target_node_id: c.targetNodeId,
-                    label: c.label || null,
-                    description: c.description || null,
-                    tags: c.tags || [],
-                    bidirectional: c.bidirectional || false,
-                    metadata: c.metadata || null,
-                }))
-                : [];
-            const boundaries = Array.isArray(sanitized.boundaries)
-                ? sanitized.boundaries.map((b) => ({
-                    boundary_id: b.id,
-                    label: b.label,
-                    description: b.description || null,
-                    color: b.color || null,
-                    position_x: b.positionX,
-                    position_y: b.positionY,
-                    width: b.width,
-                    height: b.height,
-                }))
-                : [];
             const linkedThreatModelIds = Array.isArray(sanitized.threatModelLinks)
                 ? sanitized.threatModelLinks.map((l) => l.threatModelId)
                 : [];
@@ -74,9 +27,6 @@ export function createGetDiagramHandler(apiClient) {
                 source_type: sanitized.sourceType,
                 created_at: sanitized.createdAt,
                 updated_at: sanitized.updatedAt,
-                nodes,
-                connections,
-                boundaries,
                 linked_threat_model_ids: linkedThreatModelIds,
             };
             return {

package/dist/tools/get-started.d.ts

@@ -2,7 +2,7 @@ import { z } from "zod";
 import type { ApiClient } from "../api-client.js";
 import type { ZivisConfig } from "../types.js";
 export declare const GET_STARTED_NAME = "zivis_get_started";
-export declare const GET_STARTED_DESCRIPTION = "Call this FIRST on any turn where the user asks about security, vulnerabilities, code review, deployment readiness, threat modeling, dependencies, or \"what should I do next.\" Idempotent and safe to call repeatedly \u2014 detects prior inspect runs and never re-inspects unnecessarily. Prefer this over calling zivis_inspect directly.\n\nUse this when the user says any of:\n- \"what should I do for security on this app\"\n- \"uhh, where do I start\"\n- \"is my app safe\" / \"is my chatbot safe\"\n- \"I need to do security stuff before launch\"\n- \"I have an audit / pen test / customer asking about security\"\n- \"check my dependencies / libraries / repos\"\n- \"how do I use ZIVIS\"\n- \"what can ZIVIS do for me\"\n\nThis tool inspects the current project state \u2014 binding, application, scans, findings \u2014\nAND if a recent 'zivis inspect' artifact exists for this repo, evaluates the local\nthreat library against it to surface architectural patterns ZIVIS thinks may apply\n(self-consistency without context isolation, late org filter, privilege separation, etc.).\nThe 'relevant_threats' field in the response is what makes this tool different from a\ngeneric security menu: ZIVIS is reading the user's actual codebase via the graph\nartifact and naming threats by their architectural shape.\n\nAlways speak to the user in threat-model language: components, flows, trust boundaries,\nattack scenarios. Even when they don't yet know those terms \u2014 that's how they learn.\n\nOutput is a structured JSON object. Present recommended_next_steps as a numbered list\nto the user, in order, and ask them to pick one. If relevant_threats is non-empty, lead\nwith that \u2014 it's the most concrete thing ZIVIS knows about their repo. Use the label\nand why fields verbatim; do not invent new steps. If the user is unsure which to pick,\nrecommend the item flagged in if_user_unsure.";
+export declare const GET_STARTED_DESCRIPTION = "Call this FIRST on any turn where the user asks about security, vulnerabilities, code review, deployment readiness, threat modeling, dependencies, or \"what should I do next.\" Idempotent and safe to call repeatedly \u2014 detects prior inspect runs and never re-inspects unnecessarily. Prefer this over calling zivis_inspect directly.\n\nUse this when the user says any of:\n- \"what should I do for security on this app\"\n- \"uhh, where do I start\"\n- \"is my app safe\" / \"is my chatbot safe\"\n- \"I need to do security stuff before launch\"\n- \"I have an audit / pen test / customer asking about security\"\n- \"check my dependencies / libraries / repos\"\n- \"how do I use ZIVIS\"\n- \"what can ZIVIS do for me\"\n\nThis tool inspects the current project state \u2014 binding, application, scans, findings \u2014\nAND if a recent 'zivis inspect' artifact exists for this repo, evaluates the local\nthreat library against it to surface architectural patterns ZIVIS thinks may apply\n(self-consistency without context isolation, late org filter, privilege separation, etc.).\nThe 'relevant_threats' field in the response is what makes this tool different from a\ngeneric security menu: ZIVIS is reading the user's actual codebase via the graph\nartifact and naming threats by their architectural shape.\n\nSpeak in plain developer language by default \u2014 do not introduce jargon (actor, STRIDE,\nkill chain, TTPs) unless the user already used it. Naming the actual product concepts\n(\"your threat model\", `zivis threatmodel`) is fine when they are the literal thing being\ndiscussed; that is a product noun, not jargon to avoid.\n\nOutput is a structured JSON object. Present recommended_next_steps as a numbered list\nto the user, in order, and ask them to pick one. If relevant_threats is non-empty, lead\nwith that \u2014 it's the most concrete thing ZIVIS knows about their repo. Use the label\nand why fields verbatim; do not invent new steps. If the user is unsure which to pick,\nrecommend the item flagged in if_user_unsure.";
 export declare const GET_STARTED_SCHEMA: {
     concern: z.ZodOptional<z.ZodString>;
     cwd: z.ZodOptional<z.ZodString>;

package/dist/tools/get-started.js

@@ -1,4 +1,5 @@
 import * as fs from "node:fs/promises";
+import * as path from "node:path";
 import { z } from "zod";
 import { detectProjectBinding } from "../project-binding.js";
 import { loadActivePack, findRelevantCapsules, } from "../pattern-pack/index.js";
@@ -24,8 +25,10 @@ The 'relevant_threats' field in the response is what makes this tool different f
 generic security menu: ZIVIS is reading the user's actual codebase via the graph
 artifact and naming threats by their architectural shape.
 
-Always speak to the user in threat-model language: components, flows, trust boundaries,
-attack scenarios. Even when they don't yet know those terms — that's how they learn.
+Speak in plain developer language by default — do not introduce jargon (actor, STRIDE,
+kill chain, TTPs) unless the user already used it. Naming the actual product concepts
+("your threat model", \`zivis threatmodel\`) is fine when they are the literal thing being
+discussed; that is a product noun, not jargon to avoid.
 
 Output is a structured JSON object. Present recommended_next_steps as a numbered list
 to the user, in order, and ask them to pick one. If relevant_threats is non-empty, lead
@@ -80,42 +83,44 @@ function stepCheckDeps() {
     return {
         id: "check_dependencies",
         label: "Check the open source libraries you depend on",
-        tool: "zivis_check_repo_trust",
-        why: "Free, no setup. Catches risky AI SDKs and known-bad dependencies before they cause problems.",
-        estimated_time: "1 minute per repo",
-        requires_auth: false,
+        tool: "cli_command",
+        args_hint: { command: "zivis test dependencies" },
+        why: "Runs the ZIVIS dependency-risk methodology (reachability triage) against your resolved lockfile.",
+        estimated_time: "a few minutes — the coding agent does the reasoning",
+        requires_auth: true,
     };
 }
-function stepSetupAiTarget(hint) {
+function stepTestScope(scopeId, label, why) {
     return {
-        id: "setup_ai_target",
-        label: "Tell ZIVIS about your chatbot or AI system so it can test it",
-        tool: "zivis_setup_red_team_target",
-        args_hint: { target_type: "ai_chat", ...hint },
-        why: "ZIVIS needs to know your endpoint to run prompt-injection, jailbreak, and PII-leakage tests.",
-        estimated_time: "2 minutes",
+        id: `test_${scopeId}`,
+        label,
+        tool: "cli_command",
+        args_hint: { command: `zivis test ${scopeId}` },
+        why,
+        estimated_time: "a few minutes — the coding agent does the reasoning",
         requires_auth: true,
     };
 }
-function stepSetupWebTarget(hint) {
+function stepBareTest() {
     return {
-        id: "setup_web_target",
-        label: "Register your web app or API with ZIVIS for testing",
-        tool: "zivis_setup_red_team_target",
-        args_hint: { target_type: "web_app", ...hint },
-        why: "ZIVIS needs to know your app URL to run security tests against it.",
-        estimated_time: "2 minutes",
+        id: "run_test",
+        label: "Run a ZIVIS security review of what changed",
+        tool: "cli_command",
+        args_hint: { command: "zivis test" },
+        why: "Change-aware by default: recommends only the scopes your recent changes touch, using ZIVIS's memory of what was last tested.",
+        estimated_time: "a few minutes — the coding agent does the reasoning",
         requires_auth: true,
     };
 }
-function stepBrowseTests() {
+function stepListScopes() {
     return {
-        id: "browse_test_library",
-        label: "Browse what ZIVIS can test for",
-        tool: "zivis_list_test_scenarios",
-        why: "See the menu of attack categories (prompt injection, auth bypass, data leakage, etc.) before committing to a scan.",
-        estimated_time: "30 seconds",
-        requires_auth: true,
+        id: "list_scopes",
+        label: "See the security areas ZIVIS can test",
+        tool: "cli_command",
+        args_hint: { command: "zivis test --list" },
+        why: "Lists the scopes defined by the verified ZIVIS AppSec methodology pack — pick one instead of guessing a scope name.",
+        estimated_time: "a few seconds",
+        requires_auth: false,
     };
 }
 function stepViewFindings(count) {
@@ -124,8 +129,7 @@ function stepViewFindings(count) {
         label: count
             ? `Review the ${count} open security issue${count === 1 ? "" : "s"} ZIVIS found`
             : "Review open security issues ZIVIS found",
-        tool: "zivis_get_findings",
-        args_hint: { status: "open" },
+        tool: "zivis_security_review",
         why: "Look at what's been found already before starting new scans — no point duplicating work.",
         estimated_time: "5 minutes",
         requires_auth: true,
@@ -136,18 +140,52 @@ function stepRunSecurityReview() {
         id: "run_security_review",
         label: "Get a security readiness summary before launch or audit",
         tool: "zivis_security_review",
-        why: "Pulls together all open findings, past fixes, and known attack scenarios into one pre-launch checklist.",
+        why: "Pulls together open findings and regression history from prior ZIVIS work into one pre-launch checklist.",
         estimated_time: "3 minutes",
         requires_auth: true,
     };
 }
+function stepThreatModel() {
+    return {
+        id: "threat_model",
+        label: "Start or continue this Application's living threat model",
+        tool: "cli_command",
+        args_hint: { command: "zivis threatmodel" },
+        why: "Captures components, data flows, and trust boundaries as a durable, versioned artifact.",
+        estimated_time: "a few minutes — the coding agent does the reasoning",
+        requires_auth: true,
+    };
+}
+function stepGateShip() {
+    return {
+        id: "gate_ship",
+        label: "Get a deterministic ship/no-ship verdict against your committed policy",
+        tool: "cli_command",
+        args_hint: { command: "zivis gate ship" },
+        why: "Deterministic — reads your committed .zivis/policy.yaml against live Zivis state. Never an invented verdict.",
+        estimated_time: "a few seconds",
+        requires_auth: true,
+    };
+}
+function stepGateInit() {
+    return {
+        id: "gate_init",
+        label: "Create a committed ship policy so 'can we ship?' has a real answer",
+        tool: "cli_command",
+        args_hint: { command: "zivis gate --init" },
+        why: "No .zivis/policy.yaml exists yet, so zivis gate has nothing to evaluate — this scaffolds a starter policy to review and commit.",
+        estimated_time: "a minute to review and adjust the generated thresholds",
+        requires_auth: true,
+    };
+}
 function stepSetupProject() {
     return {
         id: "setup_project",
         label: "Connect this project to your ZIVIS org",
-        tool: "zivis_check_project",
-        why: "ZIVIS needs to know which org this project belongs to before it can run tests or store results.",
-        estimated_time: "2 minutes (run 'zivis auth init' in your terminal)",
+        tool: "cli_command",
+        args_hint: { command: "zivis init" },
+        why: "Every ZIVIS command needs a bound Application before it can run tests or store results — this is the one thing that has to happen first.",
+        estimated_time: "2 minutes",
         requires_auth: false,
     };
 }
@@ -163,6 +201,10 @@ function stepInstallGitHubApp(installUrl) {
     };
 }
 async function fetchState(apiClient, cwd) {
+    const hasGatePolicy = await fs
+        .access(path.join(cwd, ".zivis", "policy.yaml"))
+        .then(() => true)
+        .catch(() => false);
     const detected = detectProjectBinding(cwd);
     if (!detected) {
         return {
@@ -171,6 +213,7 @@ async function fetchState(apiClient, cwd) {
             has_scans: false,
             has_findings: false,
             open_findings_count: 0,
+            has_gate_policy: hasGatePolicy,
         };
     }
     const state = {
@@ -180,6 +223,7 @@ async function fetchState(apiClient, cwd) {
         has_scans: false,
         has_findings: false,
         open_findings_count: 0,
+        has_gate_policy: hasGatePolicy,
     };
     try {
         const appsResp = await apiClient.get("/api/rt/applications?limit=1");
@@ -221,28 +265,19 @@ function buildMenu(intent, state, concern) {
     if (!state.bound) {
         return {
             headline: "Welcome to ZIVIS! First, let's connect this project to your organization so results are stored and tracked.",
-            recommended_next_steps: [
-                stepSetupProject(),
-                stepCheckDeps(),
-                stepBrowseTests(),
-            ],
-            guidance_for_assistant: "Present these as a numbered list. The user should run 'zivis auth init' in their terminal to complete step 1. " +
-                "Step 2 (check_dependencies) requires no auth and can be done immediately. " +
-                "If they ask 'why' something matters, expand on the 'why' field — do not make new claims.",
-            if_user_unsure: "Recommend option 2 (check_dependencies) — it requires no setup and gives immediate results.",
+            recommended_next_steps: [stepSetupProject()],
+            guidance_for_assistant: "Present this as a single step. The user should run 'zivis init' in their terminal — it handles login and " +
+                "Application binding together. Every other ZIVIS command needs this to succeed first; there is nothing " +
+                "useful to offer in parallel. If they ask 'why' something matters, expand on the 'why' field — do not make new claims.",
+            if_user_unsure: "Run 'zivis init' — it's the only step available until this project is connected.",
         };
     }
     if (state.has_findings && intent !== "dep_audit") {
         const steps = [
             stepViewFindings(state.open_findings_count),
+            stepBareTest(),
             stepCheckDeps(),
         ];
-        if (!state.has_application) {
-            steps.push(stepSetupWebTarget());
-        }
-        else {
-            steps.push(stepBrowseTests());
-        }
         return {
             headline: `ZIVIS sees your project (${state.org_name ?? "connected"}) and has found ${state.open_findings_count} open security issue${state.open_findings_count === 1 ? "" : "s"}.`,
             recommended_next_steps: steps,
@@ -253,46 +288,28 @@ function buildMenu(intent, state, concern) {
     }
     if (intent === "ai_red_team") {
         const steps = [
-            stepSetupAiTarget(),
+            stepTestScope("ai", "Test your AI system for prompt injection, jailbreaks, and data leakage", "Runs the ZIVIS 'ai' scope methodology, grounded in your actual code — not a generic checklist."),
             stepCheckDeps(),
-            stepBrowseTests(),
         ];
         return {
-            headline: state.has_application
-                ? `ZIVIS sees your project (${state.org_name ?? "connected"}) and has a target configured. Ready to test your AI system.`
-                : `ZIVIS sees your project (${state.org_name ?? "connected"}) but no security testing has run yet.`,
+            headline: `ZIVIS sees your project (${state.org_name ?? "connected"}). Let's test the AI-specific surface.`,
             recommended_next_steps: steps,
             guidance_for_assistant: "The user wants to test an AI/chatbot system. Present these as a numbered list. " +
-                "If they already have a target URL, include it in args_hint. " +
                 "If they ask 'why' something matters, expand on the 'why' field — do not make new claims.",
-            if_user_unsure: "Recommend option 1 (setup_ai_target) — setting up the chatbot as a test target is the fastest path to finding real issues.",
+            if_user_unsure: "Recommend option 1 (test_ai) — it's the scope built for exactly this.",
         };
     }
     if (intent === "dep_audit") {
         return {
-            headline: "Checking your dependencies is a great place to start — it's free, needs no setup, and often finds the most impactful issues.",
-            recommended_next_steps: [
-                stepCheckDeps(),
-                stepSetupWebTarget(),
-                stepBrowseTests(),
-            ],
-            guidance_for_assistant: "Present these as a numbered list. For step 1, ask the user to share which packages they want to check " +
-                "(the GitHub org/repo of the dependency, e.g. openai/openai-python). " +
-                "If they ask 'why' something matters, expand on the 'why' field — do not make new claims.",
-            if_user_unsure: "Recommend option 1 (check_dependencies) — it works right now with no setup.",
+            headline: "Checking your dependencies is a great place to start — it often finds the most impactful issues fastest.",
+            recommended_next_steps: [stepCheckDeps(), stepBareTest()],
+            guidance_for_assistant: "Present these as a numbered list. If they ask 'why' something matters, expand on the 'why' field — do not make new claims.",
+            if_user_unsure: "Recommend option 1 (check_dependencies).",
         };
     }
     if (intent === "pre_audit" || intent === "pre_launch") {
-        const steps = [
-            stepRunSecurityReview(),
-            stepCheckDeps(),
-        ];
-        if (!state.has_application) {
-            steps.push(stepSetupWebTarget());
-        }
-        else {
-            steps.push(stepBrowseTests());
-        }
+        const gateStep = state.has_gate_policy ? stepGateShip() : stepGateInit();
+        const steps = [stepRunSecurityReview(), gateStep, stepBareTest(), stepCheckDeps()];
         const headline = intent === "pre_audit"
             ? `ZIVIS can help you prepare for an audit. Let's get a security readiness picture first.`
             : `ZIVIS can help you check security before you go live.`;
@@ -300,47 +317,46 @@ function buildMenu(intent, state, concern) {
             headline,
             recommended_next_steps: steps,
             guidance_for_assistant: "The user has a deadline (audit or launch). Start with a security review to understand the current state, " +
-                "then address the highest-severity issues first. " +
-                "If they ask 'why' something matters, expand on the 'why' field — do not make new claims.",
-            if_user_unsure: "Recommend option 1 (run_security_review) — it gives the fastest complete picture and shows what needs to be fixed before the deadline.",
+                "then address the highest-severity issues first. The security review reflects known findings, not a " +
+                "deterministic ship verdict. If the user actually asks 'can we ship?' / 'go or no-go?', route to " +
+                "'zivis gate' — NEVER answer that question yourself from the review or from general judgment. " +
+                (state.has_gate_policy
+                    ? "A committed policy already exists here, so 'zivis gate ship' (or the relevant gate name) gives a real deterministic answer."
+                    : "No committed policy exists yet, so gate has nothing to evaluate — offer 'zivis gate --init' to scaffold one first, then run the real evaluation. Do not substitute your own opinion in the meantime.") +
+                " If they ask 'why' something matters, expand on the 'why' field — do not make new claims.",
+            if_user_unsure: "Recommend option 1 (run_security_review) — it gives the fastest complete picture of what's already known.",
         };
     }
     if (intent === "view_findings") {
         return {
             headline: state.has_findings
                 ? `ZIVIS has ${state.open_findings_count} open finding${state.open_findings_count === 1 ? "" : "s"} for this project.`
-                : `No open findings found yet — ZIVIS may not have run a scan, or all issues are resolved.`,
+                : `No open findings on record yet — that means no test has found one, not that the project is clean.`,
             recommended_next_steps: [
                 stepViewFindings(state.open_findings_count > 0 ? state.open_findings_count : undefined),
-                state.has_application ? stepBrowseTests() : stepSetupWebTarget(),
-                stepCheckDeps(),
+                stepBareTest(),
             ],
-            guidance_for_assistant: "Present these as a numbered list. If the user wants to see findings, call zivis_get_findings directly. " +
+            guidance_for_assistant: "Present these as a numbered list. If the user wants to see findings, call zivis_security_review directly. " +
+                "No open findings does not mean the project passed a test — say so explicitly if the count is zero. " +
                 "If they ask 'why' something matters, expand on the 'why' field — do not make new claims.",
             if_user_unsure: "Recommend option 1 (view_open_findings) — let's see what ZIVIS already knows.",
         };
     }
-    const steps = [];
-    if (!state.has_application) {
-        steps.push(stepSetupWebTarget());
-    }
-    steps.push(stepCheckDeps());
+    const steps = [stepBareTest(), stepCheckDeps()];
     if (state.has_findings) {
         steps.push(stepViewFindings(state.open_findings_count));
     }
     else {
-        steps.push(stepBrowseTests());
+        steps.push(stepListScopes());
     }
-    if (steps.length < 3)
-        steps.push(stepBrowseTests());
+    if (!state.has_application)
+        steps.push(stepThreatModel());
     return {
-        headline: state.has_application
-            ? `ZIVIS is connected to your project (${state.org_name ?? "org"}). Here are the most useful things to do next.`
-            : `ZIVIS is connected to your project (${state.org_name ?? "org"}) but no app has been registered for testing yet.`,
+        headline: `ZIVIS is connected to your project (${state.org_name ?? "org"}). Here are the most useful things to do next.`,
         recommended_next_steps: steps.slice(0, 4),
         guidance_for_assistant: "Present these as a numbered list. Ask the user to pick one before taking any action. " +
             "If they ask 'why' something matters, expand on the 'why' field — do not make new claims.",
-        if_user_unsure: "Recommend option 2 (check_dependencies) — it's free, fast, and shows value without setup.",
+        if_user_unsure: "Recommend option 1 (run_test) — bare 'zivis test' is change-aware and the natural default entry point.",
     };
 }
 async function findRelevantThreats(cwd) {

package/dist/tools/get-trust-keys.d.ts

@@ -1,6 +1,6 @@
 import type { ZivisConfig } from "../types.js";
 export declare const GET_TRUST_KEYS_NAME = "zivis_get_trust_keys";
-export declare const GET_TRUST_KEYS_DESCRIPTION = "Retrieve the ZIVIS public signing keys (JWKS) for independent cryptographic verification of trust marks and ZATs.\n\nReturns a JWKS (JSON Web Key Set) containing two keys:\n\n1. **ML-DSA-65 key** (post-quantum, FIPS-204):\n   - Algorithm: CRYSTALS-Dilithium Level 3\n   - NIST Security Category 3 (128-bit quantum security)\n   - Used to verify the full digital signature on ZATs and trust marks\n   - Key type: \"PQ-LWE\" (proposed post-quantum JWK key type)\n   - The \"x\" field is the base64url-encoded public key bytes\n\n2. **Ed25519 key** (RFC 8032):\n   - Used to verify compact trust tokens (shorter, URL-safe format)\n   - Standard JWK format (kty: \"OKP\", crv: \"Ed25519\")\n\nThese keys enable third-party, offline verification without trusting ZIVIS infrastructure.\nThis is critical for ATNP (Agent Trust Negotiation Protocol) where agents must independently verify trust marks.\n\nVerification workflow:\n1. Get a ZAT (from zivis_get_oss_zat or zivis_get_org_zat)\n2. Get the public keys (this tool)\n3. Verify the signature using ML-DSA-65 or Ed25519 library of your choice\n4. Check expiration and claims\n\nNo parameters required. No authentication required.";
+export declare const GET_TRUST_KEYS_DESCRIPTION = "Retrieve the ZIVIS public signing keys (JWKS) for independent cryptographic verification of trust marks and ZATs.\n\nReturns a JWKS (JSON Web Key Set) containing two keys:\n\n1. **ML-DSA-65 key** (post-quantum, FIPS-204):\n   - Algorithm: CRYSTALS-Dilithium Level 3\n   - NIST Security Category 3 (128-bit quantum security)\n   - Used to verify the full digital signature on ZATs and trust marks\n   - Key type: \"PQ-LWE\" (proposed post-quantum JWK key type)\n   - The \"x\" field is the base64url-encoded public key bytes\n\n2. **Ed25519 key** (RFC 8032):\n   - Used to verify compact trust tokens (shorter, URL-safe format)\n   - Standard JWK format (kty: \"OKP\", crv: \"Ed25519\")\n\nThese keys enable third-party, offline verification without trusting ZIVIS infrastructure.\nThis is critical for ATNP (Agent Trust Negotiation Protocol) where agents must independently verify trust marks.\n\nVerification workflow:\n1. Get a ZAT (from zivis_get_org_zat)\n2. Get the public keys (this tool)\n3. Verify the signature using ML-DSA-65 or Ed25519 library of your choice\n4. Check expiration and claims\n\nNo parameters required. No authentication required.";
 export declare const GET_TRUST_KEYS_SCHEMA: {};
 export declare function createGetTrustKeysHandler(config: ZivisConfig): () => Promise<{
     content: {

package/dist/tools/get-trust-keys.js

@@ -18,7 +18,7 @@ These keys enable third-party, offline verification without trusting ZIVIS infra
 This is critical for ATNP (Agent Trust Negotiation Protocol) where agents must independently verify trust marks.
 
 Verification workflow:
-1. Get a ZAT (from zivis_get_oss_zat or zivis_get_org_zat)
+1. Get a ZAT (from zivis_get_org_zat)
 2. Get the public keys (this tool)
 3. Verify the signature using ML-DSA-65 or Ed25519 library of your choice
 4. Check expiration and claims

package/dist/tools/inspect-zat.d.ts

@@ -1,6 +1,6 @@
 import { z } from "zod";
 export declare const INSPECT_ZAT_NAME = "zivis_inspect_zat";
-export declare const INSPECT_ZAT_DESCRIPTION = "Parse a ZIVIS Attestation Token (ZAT) JSON and produce a human-readable explanation of all fields.\n\nThis tool does NOT make any API calls \u2014 it parses the ZAT locally and explains what each field means.\n\nUse this after retrieving a ZAT from zivis_get_oss_zat or zivis_get_org_zat to understand:\n- What the claims mean (Z-Score, trust tiers, coverage, findings)\n- Whether signatures are present and which algorithms were used\n- Token validity and expiration\n- Evidence manifest integrity\n- Framework and methodology details\n- Lens-level scores (for OSS ZATs)\n\nAccepts either:\n- A JSON string (the raw ZAT output)\n- A JSON object with a \"zat\" field (the wrapper returned by the API)\n\nZAT Field Reference:\n- **iss**: Issuer (always \"zivis.ai\")\n- **sub**: Subject \u2014 \"org:<slug>\" for enterprise, \"github:<owner>/<repo>\" for OSS\n- **mark_id**: Unique identifier (ztm_...) \u2014 references the trust mark\n- **issued_at / expires_at**: ISO 8601 timestamps \u2014 ZATs are short-lived (48h)\n- **frameworks[]**: Which security frameworks were assessed (NIST IR 8596, ISO 42001, OWASP LLM Top 10, etc.)\n  - basis: \"tested\" | \"mapped\" | \"self-attested\" | \"third-party\" \u2014 how the assessment was performed\n  - csf_version: Present if framework is NIST CSF 2.0 derived (enables cross-framework comparison)\n- **claims**: The actual trust posture\n  - For enterprise: z_score_raw (0-1), z_score_display (0-1000), tier (0-3), tier_label, coverage_pct, mapped_outcomes\n  - For OSS: score (0-100), grade (A+ to F), check_types, findings by severity, commit SHA\n  - Tier meanings: 0=Commitment, 1=Foundational Trust (600+), 2=Operational Trust (700+), 3=Systemic Trust (800+)\n- **evidence_manifest**: SHA-256 hash of the evidence bundle \u2014 proves the assessment data hasn't been tampered with\n- **methodology**: How the assessment was performed (model version, scoring algorithm, evaluator type)\n- **sig**: Cryptographic signatures\n  - alg: \"ML-DSA-65\" (FIPS-204, post-quantum CRYSTALS-Dilithium Level 3)\n  - compact: Ed25519 (RFC 8032) compact token for lightweight verification\n- **ver**: ZAT spec version (e.g., \"0.3.0\")";
+export declare const INSPECT_ZAT_DESCRIPTION = "Parse a ZIVIS Attestation Token (ZAT) JSON and produce a human-readable explanation of all fields.\n\nThis tool does NOT make any API calls \u2014 it parses the ZAT locally and explains what each field means.\n\nUse this after retrieving a ZAT from zivis_get_org_zat to understand:\n- What the claims mean (Z-Score, trust tiers, coverage, findings)\n- Whether signatures are present and which algorithms were used\n- Token validity and expiration\n- Evidence manifest integrity\n- Framework and methodology details\n- Lens-level scores (for OSS ZATs)\n\nAccepts either:\n- A JSON string (the raw ZAT output)\n- A JSON object with a \"zat\" field (the wrapper returned by the API)\n\nZAT Field Reference:\n- **iss**: Issuer (always \"zivis.ai\")\n- **sub**: Subject \u2014 \"org:<slug>\" for enterprise, \"github:<owner>/<repo>\" for OSS\n- **mark_id**: Unique identifier (ztm_...) \u2014 references the trust mark\n- **issued_at / expires_at**: ISO 8601 timestamps \u2014 ZATs are short-lived (48h)\n- **frameworks[]**: Which security frameworks were assessed (NIST IR 8596, ISO 42001, OWASP LLM Top 10, etc.)\n  - basis: \"tested\" | \"mapped\" | \"self-attested\" | \"third-party\" \u2014 how the assessment was performed\n  - csf_version: Present if framework is NIST CSF 2.0 derived (enables cross-framework comparison)\n- **claims**: The actual trust posture\n  - For enterprise: z_score_raw (0-1), z_score_display (0-1000), tier (0-3), tier_label, coverage_pct, mapped_outcomes\n  - For OSS: score (0-100), grade (A+ to F), check_types, findings by severity, commit SHA\n  - Tier meanings: 0=Commitment, 1=Foundational Trust (600+), 2=Operational Trust (700+), 3=Systemic Trust (800+)\n- **evidence_manifest**: SHA-256 hash of the evidence bundle \u2014 proves the assessment data hasn't been tampered with\n- **methodology**: How the assessment was performed (model version, scoring algorithm, evaluator type)\n- **sig**: Cryptographic signatures\n  - alg: \"ML-DSA-65\" (FIPS-204, post-quantum CRYSTALS-Dilithium Level 3)\n  - compact: Ed25519 (RFC 8032) compact token for lightweight verification\n- **ver**: ZAT spec version (e.g., \"0.3.0\")";
 export declare const INSPECT_ZAT_SCHEMA: {
     zat_json: z.ZodString;
 };

package/dist/tools/inspect-zat.js

@@ -4,7 +4,7 @@ export const INSPECT_ZAT_DESCRIPTION = `Parse a ZIVIS Attestation Token (ZAT) JS
 
 This tool does NOT make any API calls — it parses the ZAT locally and explains what each field means.
 
-Use this after retrieving a ZAT from zivis_get_oss_zat or zivis_get_org_zat to understand:
+Use this after retrieving a ZAT from zivis_get_org_zat to understand:
 - What the claims mean (Z-Score, trust tiers, coverage, findings)
 - Whether signatures are present and which algorithms were used
 - Token validity and expiration
@@ -37,7 +37,7 @@ ZAT Field Reference:
 export const INSPECT_ZAT_SCHEMA = {
     zat_json: z
         .string()
-        .describe("The ZAT JSON string to inspect (from zivis_get_oss_zat or zivis_get_org_zat output)"),
+        .describe("The ZAT JSON string to inspect (from zivis_get_org_zat output)"),
 };
 export function createInspectZatHandler() {
     return async (params) => {

package/dist/tools/list-diagrams.d.ts

@@ -1,7 +1,7 @@
 import { z } from "zod";
 import type { ApiClient } from "../api-client.js";
 export declare const LIST_DIAGRAMS_NAME = "zivis_list_diagrams";
-export declare const LIST_DIAGRAMS_DESCRIPTION = "List diagrams for your organization. Returns summary info (name, type, node/connection counts) for each diagram.\n\nUse this tool to find existing diagrams before modifying them. To get the full content (nodes, connections, boundaries), use zivis_get_diagram with the diagram_id from this response.\n\nDiagrams can be linked to threat models. Use linked_threat_model_id to find diagrams for a specific threat model.";
+export declare const LIST_DIAGRAMS_DESCRIPTION = "List diagrams for your organization. Returns summary info (name, type, description) for each diagram.\n\nUse this tool to find existing diagrams before modifying them. To get the full content (Mermaid source), use zivis_get_diagram with the diagram_id from this response.\n\nDiagrams can be linked to threat models. Use linked_threat_model_id to find diagrams for a specific threat model.";
 export declare const LIST_DIAGRAMS_SCHEMA: {
     diagram_type: z.ZodOptional<z.ZodEnum<{
         custom: "custom";

package/dist/tools/list-diagrams.js

@@ -1,9 +1,9 @@
 import { z } from "zod";
 import { sanitizeResponse } from "../sanitize.js";
 export const LIST_DIAGRAMS_NAME = "zivis_list_diagrams";
-export const LIST_DIAGRAMS_DESCRIPTION = `List diagrams for your organization. Returns summary info (name, type, node/connection counts) for each diagram.
+export const LIST_DIAGRAMS_DESCRIPTION = `List diagrams for your organization. Returns summary info (name, type, description) for each diagram.
 
-Use this tool to find existing diagrams before modifying them. To get the full content (nodes, connections, boundaries), use zivis_get_diagram with the diagram_id from this response.
+Use this tool to find existing diagrams before modifying them. To get the full content (Mermaid source), use zivis_get_diagram with the diagram_id from this response.
 
 Diagrams can be linked to threat models. Use linked_threat_model_id to find diagrams for a specific threat model.`;
 export const LIST_DIAGRAMS_SCHEMA = {
@@ -52,7 +52,6 @@ export function createListDiagramsHandler(apiClient) {
                     description: d.description || null,
                     created_at: d.createdAt,
                     updated_at: d.updatedAt,
-                    stats: d._count || null,
                 }))
                 : sanitized.diagrams;
             return {

package/dist/tools/manage-diagram.d.ts

@@ -1,21 +1,12 @@
 import { z } from "zod";
 import type { ApiClient } from "../api-client.js";
 export declare const MANAGE_DIAGRAM_NAME = "zivis_manage_diagram";
-export declare const MANAGE_DIAGRAM_DESCRIPTION = "Modify an existing diagram: update metadata, add/update/delete nodes, connections, and boundaries, or link/unlink threat models.\n\n**Before modifying:** Use zivis_get_diagram to fetch current content and get node/connection/boundary IDs.\n\nActions:\n- update_metadata: Update diagram name, description, or type\n- delete_diagram: Delete the entire diagram\n- add_node: Add a new node (requires node_name)\n- update_node: Update an existing node (requires node_id)\n- delete_node: Remove a node (requires node_id)\n- add_connection: Add a connection between two nodes (requires source_node_id, target_node_id)\n- update_connection: Update a connection (requires connection_id)\n- delete_connection: Remove a connection (requires connection_id)\n- add_boundary: Add a boundary group (requires boundary_label)\n- update_boundary: Update a boundary (requires boundary_id)\n- delete_boundary: Remove a boundary (requires boundary_id)\n- link_threat_model: Link diagram to a threat model (requires threat_model_id)\n- unlink_threat_model: Unlink from a threat model (requires threat_model_id)";
+export declare const MANAGE_DIAGRAM_DESCRIPTION = "Modify an existing diagram: update metadata, delete it, or link/unlink it to a threat model.\n\nTo change a diagram's Mermaid source, use zivis_update_mermaid_source instead.\n\nActions:\n- update_metadata: Update diagram name, description, or type\n- delete_diagram: Delete the entire diagram\n- link_threat_model: Link diagram to a threat model (requires threat_model_id)\n- unlink_threat_model: Unlink from a threat model (requires threat_model_id)";
 export declare const MANAGE_DIAGRAM_SCHEMA: {
     diagram_id: z.ZodString;
     action: z.ZodEnum<{
         update_metadata: "update_metadata";
         delete_diagram: "delete_diagram";
-        add_node: "add_node";
-        update_node: "update_node";
-        delete_node: "delete_node";
-        add_connection: "add_connection";
-        update_connection: "update_connection";
-        delete_connection: "delete_connection";
-        add_boundary: "add_boundary";
-        update_boundary: "update_boundary";
-        delete_boundary: "delete_boundary";
         link_threat_model: "link_threat_model";
         unlink_threat_model: "unlink_threat_model";
     }>;
@@ -31,33 +22,6 @@ export declare const MANAGE_DIAGRAM_SCHEMA: {
         trust_boundary: "trust_boundary";
         network: "network";
     }>>;
-    node_id: z.ZodOptional<z.ZodString>;
-    node_name: z.ZodOptional<z.ZodString>;
-    node_description: z.ZodOptional<z.ZodString>;
-    node_tags: z.ZodOptional<z.ZodArray<z.ZodString>>;
-    node_icon: z.ZodOptional<z.ZodString>;
-    node_color: z.ZodOptional<z.ZodString>;
-    position_x: z.ZodOptional<z.ZodNumber>;
-    position_y: z.ZodOptional<z.ZodNumber>;
-    width: z.ZodOptional<z.ZodNumber>;
-    height: z.ZodOptional<z.ZodNumber>;
-    step_order: z.ZodOptional<z.ZodNumber>;
-    boundary_id: z.ZodOptional<z.ZodString>;
-    metadata: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
-    connection_id: z.ZodOptional<z.ZodString>;
-    source_node_id: z.ZodOptional<z.ZodString>;
-    target_node_id: z.ZodOptional<z.ZodString>;
-    label: z.ZodOptional<z.ZodString>;
-    connection_description: z.ZodOptional<z.ZodString>;
-    connection_tags: z.ZodOptional<z.ZodArray<z.ZodString>>;
-    bidirectional: z.ZodOptional<z.ZodBoolean>;
-    boundary_label: z.ZodOptional<z.ZodString>;
-    boundary_description: z.ZodOptional<z.ZodString>;
-    boundary_color: z.ZodOptional<z.ZodString>;
-    boundary_position_x: z.ZodOptional<z.ZodNumber>;
-    boundary_position_y: z.ZodOptional<z.ZodNumber>;
-    boundary_width: z.ZodOptional<z.ZodNumber>;
-    boundary_height: z.ZodOptional<z.ZodNumber>;
     threat_model_id: z.ZodOptional<z.ZodString>;
 };
 type ManageDiagramParams = {
@@ -66,33 +30,6 @@ type ManageDiagramParams = {
     name?: string;
     description?: string;
     diagram_type?: string;
-    node_id?: string;
-    node_name?: string;
-    node_description?: string;
-    node_tags?: string[];
-    node_icon?: string;
-    node_color?: string;
-    position_x?: number;
-    position_y?: number;
-    width?: number;
-    height?: number;
-    step_order?: number;
-    boundary_id?: string;
-    metadata?: Record<string, unknown>;
-    connection_id?: string;
-    source_node_id?: string;
-    target_node_id?: string;
-    label?: string;
-    connection_description?: string;
-    connection_tags?: string[];
-    bidirectional?: boolean;
-    boundary_label?: string;
-    boundary_description?: string;
-    boundary_color?: string;
-    boundary_position_x?: number;
-    boundary_position_y?: number;
-    boundary_width?: number;
-    boundary_height?: number;
     threat_model_id?: string;
 };
 export declare function createManageDiagramHandler(apiClient: ApiClient): (params: ManageDiagramParams) => Promise<{