@zivis/mcp 0.1.0-alpha.9 → 0.1.6

package/dist/tools/enterprise/manage-actor.d.ts

@@ -1,12 +1,7 @@
-/**
- * zivis_manage_actor — Create, update, or delete threat actors in a threat model
- *
- * Maps to: POST/PATCH/DELETE /api/threat-models/:id/actors
- */
 import { z } from "zod";
 import type { ApiClient } from "../../api-client.js";
 export declare const MANAGE_ACTOR_NAME = "zivis_manage_actor";
-export declare const MANAGE_ACTOR_DESCRIPTION = "Create, update, or delete a threat actor in a threat model.\n\nThreat actors represent entities that interact with or threaten the system (e.g., external users, attackers, services). Each actor has a trust level, type, and capabilities.\n\nActions:\n- create: Add a new threat actor (requires name, actor_type, trust_level)\n- update: Modify an existing actor (requires actor_id)\n- delete: Remove an actor (requires actor_id)";
+export declare const MANAGE_ACTOR_DESCRIPTION = "Create, update, or delete a threat actor in a threat model.\n\nWhen to use (plain English): call this when the user describes who interacts with or threatens the app. Common phrasings:\n- \"users / end users / customers / our users can ...\"\n- \"admins / support team / internal employees ...\"\n- \"attacker / adversary / bad actor / malicious user ...\"\n- \"insider / rogue employee ...\"\n- \"vendor / partner / integration partner ...\"\n- \"bot / scraper / automated agent ...\"\n- \"<external service> calls our API\" (the external service is an actor too)\n\n\nThreat actors represent entities that interact with or threaten the system. Each actor has a trust level, type, and capabilities.\n\nAfter create: ask which components this actor interacts with so a data flow can be modeled.\n\nActions:\n- create: Add a new threat actor (requires name, actor_type, trust_level)\n- update: Modify an existing actor (requires actor_id)\n- delete: Remove an actor (requires actor_id)";
 export declare const MANAGE_ACTOR_SCHEMA: {
     threat_model_id: z.ZodString;
     action: z.ZodEnum<{
@@ -17,10 +12,10 @@ export declare const MANAGE_ACTOR_SCHEMA: {
     actor_id: z.ZodOptional<z.ZodString>;
     name: z.ZodOptional<z.ZodString>;
     actor_type: z.ZodOptional<z.ZodEnum<{
+        third_party: "third_party";
         external: "external";
         internal: "internal";
         system: "system";
-        third_party: "third_party";
     }>>;
     trust_level: z.ZodOptional<z.ZodEnum<{
         high: "high";

package/dist/tools/enterprise/manage-actor.js

@@ -1,14 +1,21 @@
-/**
- * zivis_manage_actor — Create, update, or delete threat actors in a threat model
- *
- * Maps to: POST/PATCH/DELETE /api/threat-models/:id/actors
- */
 import { z } from "zod";
 import { sanitizeResponse } from "../../sanitize.js";
 export const MANAGE_ACTOR_NAME = "zivis_manage_actor";
 export const MANAGE_ACTOR_DESCRIPTION = `Create, update, or delete a threat actor in a threat model.
 
-Threat actors represent entities that interact with or threaten the system (e.g., external users, attackers, services). Each actor has a trust level, type, and capabilities.
+When to use (plain English): call this when the user describes who interacts with or threatens the app. Common phrasings:
+- "users / end users / customers / our users can ..."
+- "admins / support team / internal employees ..."
+- "attacker / adversary / bad actor / malicious user ..."
+- "insider / rogue employee ..."
+- "vendor / partner / integration partner ..."
+- "bot / scraper / automated agent ..."
+- "<external service> calls our API" (the external service is an actor too)
+
+
+Threat actors represent entities that interact with or threaten the system. Each actor has a trust level, type, and capabilities.
+
+After create: ask which components this actor interacts with so a data flow can be modeled.
 
 Actions:
 - create: Add a new threat actor (requires name, actor_type, trust_level)
@@ -96,4 +103,3 @@ export function createManageActorHandler(apiClient) {
         }
     };
 }
-//# sourceMappingURL=manage-actor.js.map

package/dist/tools/enterprise/manage-attack-scenario.d.ts

@@ -1,12 +1,7 @@
-/**
- * zivis_manage_attack_scenario — Create, update, or delete attack scenarios
- *
- * Maps to: POST/PATCH/DELETE /api/threat-models/:id/attack-scenarios
- */
 import { z } from "zod";
 import type { ApiClient } from "../../api-client.js";
 export declare const MANAGE_ATTACK_SCENARIO_NAME = "zivis_manage_attack_scenario";
-export declare const MANAGE_ATTACK_SCENARIO_DESCRIPTION = "Create, update, or delete an attack scenario in a threat model.\n\nAttack scenarios describe specific attack paths \u2014 how a threat actor could exploit vulnerabilities to achieve their objective. They link actors, components, and attack vectors into a cohesive narrative.\n\nActions:\n- create: Add a new scenario (requires title, narrative, entry_point_id, target_id)\n- update: Update scenario status/notes (requires scenario_id)\n- delete: Remove a scenario (requires scenario_id)";
+export declare const MANAGE_ATTACK_SCENARIO_DESCRIPTION = "Create, update, or delete an attack scenario in a threat model.\n\nWhen to use (plain English): call this when the user describes a security worry, \"what if\" question, or specific failure mode. Common phrasings:\n- \"what if <bad thing happens>\"\n- \"could someone <attack action>\"\n- \"I'm worried about <X> being abused / leaked / hacked\"\n- \"how would an attacker <do X>\"\n- \"is <Y> safe from <Z>\"\n- mentions of: prompt injection, jailbreak, data exfiltration, privilege escalation, account takeover, supply chain, abuse\n\nBefore creating a scenario, the threat model needs at least one entry_point component (where the attack starts) and a target component (where the attacker wants to go). If either is missing, model components first.\n\nThe narrative should be a 2\u20135 sentence story: who attacks, where they enter, what they exploit, what they achieve. Don't write a textbook chapter.\n\n\nActions:\n- create: Add a new scenario (requires title, narrative, entry_point_id, target_id)\n- update: Update scenario status/notes (requires scenario_id)\n- delete: Remove a scenario (requires scenario_id)";
 export declare const MANAGE_ATTACK_SCENARIO_SCHEMA: {
     threat_model_id: z.ZodString;
     action: z.ZodEnum<{

package/dist/tools/enterprise/manage-attack-scenario.js

@@ -1,14 +1,20 @@
-/**
- * zivis_manage_attack_scenario — Create, update, or delete attack scenarios
- *
- * Maps to: POST/PATCH/DELETE /api/threat-models/:id/attack-scenarios
- */
 import { z } from "zod";
 import { sanitizeResponse } from "../../sanitize.js";
 export const MANAGE_ATTACK_SCENARIO_NAME = "zivis_manage_attack_scenario";
 export const MANAGE_ATTACK_SCENARIO_DESCRIPTION = `Create, update, or delete an attack scenario in a threat model.
 
-Attack scenarios describe specific attack paths — how a threat actor could exploit vulnerabilities to achieve their objective. They link actors, components, and attack vectors into a cohesive narrative.
+When to use (plain English): call this when the user describes a security worry, "what if" question, or specific failure mode. Common phrasings:
+- "what if <bad thing happens>"
+- "could someone <attack action>"
+- "I'm worried about <X> being abused / leaked / hacked"
+- "how would an attacker <do X>"
+- "is <Y> safe from <Z>"
+- mentions of: prompt injection, jailbreak, data exfiltration, privilege escalation, account takeover, supply chain, abuse
+
+Before creating a scenario, the threat model needs at least one entry_point component (where the attack starts) and a target component (where the attacker wants to go). If either is missing, model components first.
+
+The narrative should be a 2–5 sentence story: who attacks, where they enter, what they exploit, what they achieve. Don't write a textbook chapter.
+
 
 Actions:
 - create: Add a new scenario (requires title, narrative, entry_point_id, target_id)
@@ -86,4 +92,3 @@ export function createManageAttackScenarioHandler(apiClient) {
         }
     };
 }
-//# sourceMappingURL=manage-attack-scenario.js.map

package/dist/tools/enterprise/manage-data-asset.d.ts

@@ -1,12 +1,7 @@
-/**
- * zivis_manage_data_asset — Create, update, or delete data assets
- *
- * Maps to: POST/PATCH/DELETE /api/threat-models/:id/data-assets
- */
 import { z } from "zod";
 import type { ApiClient } from "../../api-client.js";
 export declare const MANAGE_DATA_ASSET_NAME = "zivis_manage_data_asset";
-export declare const MANAGE_DATA_ASSET_DESCRIPTION = "Create, update, or delete a data asset in a threat model.\n\nData assets represent sensitive data that needs protection (e.g., user PII, API keys, session tokens, financial records).\n\nActions:\n- create: Add a new data asset (requires name, classification)\n- update: Modify an existing data asset (requires asset_id)\n- delete: Remove a data asset (requires asset_id)";
+export declare const MANAGE_DATA_ASSET_DESCRIPTION = "Create, update, or delete a data asset in a threat model.\n\nWhen to use (plain English): call this when the user names something the app stores or processes. Common phrasings:\n- \"we store <PII / credit card / passwords / session tokens / api keys / audit logs>\"\n- \"the <user / customer / patient> data is in <storage>\"\n- \"we keep <emails / phone numbers / SSN / addresses>\"\n- \"<asset> is encrypted at rest\" \u2014 model the asset, then a security control on top of it\n- \"we hold cardholder data\" / \"we handle payment cards\" \u2192 classification=restricted, data_type=payment_data\n\nPick classification:\n- public \u2014 anyone can see (marketing copy)\n- internal \u2014 employees only (org chart, internal docs)\n- confidential \u2014 PII, business confidential\n- restricted \u2014 payment data, health records, anything regulated\n- critical \u2014 credentials, secrets, root keys, anything an attacker would target first\n\n\nAfter create: ask which components store, process, or transmit this asset so coverage can be linked. If the asset is sensitive (confidential or higher) and no security control covers it, surface that gap.\n\nActions:\n- create: Add a new data asset (requires name, classification)\n- update: Modify an existing data asset (requires asset_id)\n- delete: Remove a data asset (requires asset_id)";
 export declare const MANAGE_DATA_ASSET_SCHEMA: {
     threat_model_id: z.ZodString;
     action: z.ZodEnum<{
@@ -18,8 +13,8 @@ export declare const MANAGE_DATA_ASSET_SCHEMA: {
     name: z.ZodOptional<z.ZodString>;
     classification: z.ZodOptional<z.ZodEnum<{
         critical: "critical";
-        internal: "internal";
         public: "public";
+        internal: "internal";
         confidential: "confidential";
         restricted: "restricted";
     }>>;

package/dist/tools/enterprise/manage-data-asset.js

@@ -1,14 +1,24 @@
-/**
- * zivis_manage_data_asset — Create, update, or delete data assets
- *
- * Maps to: POST/PATCH/DELETE /api/threat-models/:id/data-assets
- */
 import { z } from "zod";
 import { sanitizeResponse } from "../../sanitize.js";
 export const MANAGE_DATA_ASSET_NAME = "zivis_manage_data_asset";
 export const MANAGE_DATA_ASSET_DESCRIPTION = `Create, update, or delete a data asset in a threat model.
 
-Data assets represent sensitive data that needs protection (e.g., user PII, API keys, session tokens, financial records).
+When to use (plain English): call this when the user names something the app stores or processes. Common phrasings:
+- "we store <PII / credit card / passwords / session tokens / api keys / audit logs>"
+- "the <user / customer / patient> data is in <storage>"
+- "we keep <emails / phone numbers / SSN / addresses>"
+- "<asset> is encrypted at rest" — model the asset, then a security control on top of it
+- "we hold cardholder data" / "we handle payment cards" → classification=restricted, data_type=payment_data
+
+Pick classification:
+- public — anyone can see (marketing copy)
+- internal — employees only (org chart, internal docs)
+- confidential — PII, business confidential
+- restricted — payment data, health records, anything regulated
+- critical — credentials, secrets, root keys, anything an attacker would target first
+
+
+After create: ask which components store, process, or transmit this asset so coverage can be linked. If the asset is sensitive (confidential or higher) and no security control covers it, surface that gap.
 
 Actions:
 - create: Add a new data asset (requires name, classification)
@@ -87,4 +97,3 @@ export function createManageDataAssetHandler(apiClient) {
         }
     };
 }
-//# sourceMappingURL=manage-data-asset.js.map

package/dist/tools/enterprise/manage-security-control.d.ts

@@ -1,12 +1,7 @@
-/**
- * zivis_manage_security_control — Create, update, or delete security controls
- *
- * Maps to: POST/PATCH/DELETE /api/threat-models/:id/security-controls
- */
 import { z } from "zod";
 import type { ApiClient } from "../../api-client.js";
 export declare const MANAGE_SECURITY_CONTROL_NAME = "zivis_manage_security_control";
-export declare const MANAGE_SECURITY_CONTROL_DESCRIPTION = "Create, update, or delete a security control in a threat model.\n\nSecurity controls are mitigations that reduce or eliminate threats (e.g., input validation, rate limiting, encryption at rest).\n\nActions:\n- create: Add a new control (requires name, control_type)\n- update: Modify an existing control (requires control_id)\n- delete: Remove a control (requires control_id)";
+export declare const MANAGE_SECURITY_CONTROL_DESCRIPTION = "Create, update, or delete a security control in a threat model.\n\nWhen to use (plain English): call this when the user mentions a protective mechanism that's in place (or planned). Common phrasings:\n- \"we have <rate limiting / WAF / firewall / MFA / 2FA / encryption>\"\n- \"we sanitize / validate <inputs>\"\n- \"we encrypt <X> at rest / in transit\"\n- \"we audit log all <Y>\"\n- \"<Z> is behind auth / behind a VPN\"\n- \"we use TLS for everything\"\n\nPick control_type:\n- preventive \u2014 stops the threat before it happens (input validation, rate limiting, encryption, MFA)\n- detective \u2014 notices when something bad happens (audit logging, monitoring, alerts, anomaly detection)\n- responsive \u2014 reacts to a known incident (auto-block, key rotation, account lockout)\n\nSet component_id when the control applies to one specific component. Leave it blank for org-wide controls (e.g., \"we use a WAF in front of everything\").\n\n\nAfter create: if a sensitive data asset (PII / payment / credentials) exists with no controls covering it, that's a high-priority gap \u2014 flag it.\n\nActions:\n- create: Add a new control (requires name, control_type)\n- update: Modify an existing control (requires control_id)\n- delete: Remove a control (requires control_id)";
 export declare const MANAGE_SECURITY_CONTROL_SCHEMA: {
     threat_model_id: z.ZodString;
     action: z.ZodEnum<{

package/dist/tools/enterprise/manage-security-control.js

@@ -1,14 +1,25 @@
-/**
- * zivis_manage_security_control — Create, update, or delete security controls
- *
- * Maps to: POST/PATCH/DELETE /api/threat-models/:id/security-controls
- */
 import { z } from "zod";
 import { sanitizeResponse } from "../../sanitize.js";
 export const MANAGE_SECURITY_CONTROL_NAME = "zivis_manage_security_control";
 export const MANAGE_SECURITY_CONTROL_DESCRIPTION = `Create, update, or delete a security control in a threat model.
 
-Security controls are mitigations that reduce or eliminate threats (e.g., input validation, rate limiting, encryption at rest).
+When to use (plain English): call this when the user mentions a protective mechanism that's in place (or planned). Common phrasings:
+- "we have <rate limiting / WAF / firewall / MFA / 2FA / encryption>"
+- "we sanitize / validate <inputs>"
+- "we encrypt <X> at rest / in transit"
+- "we audit log all <Y>"
+- "<Z> is behind auth / behind a VPN"
+- "we use TLS for everything"
+
+Pick control_type:
+- preventive — stops the threat before it happens (input validation, rate limiting, encryption, MFA)
+- detective — notices when something bad happens (audit logging, monitoring, alerts, anomaly detection)
+- responsive — reacts to a known incident (auto-block, key rotation, account lockout)
+
+Set component_id when the control applies to one specific component. Leave it blank for org-wide controls (e.g., "we use a WAF in front of everything").
+
+
+After create: if a sensitive data asset (PII / payment / credentials) exists with no controls covering it, that's a high-priority gap — flag it.
 
 Actions:
 - create: Add a new control (requires name, control_type)
@@ -93,4 +104,3 @@ export function createManageSecurityControlHandler(apiClient) {
         }
     };
 }
-//# sourceMappingURL=manage-security-control.js.map

package/dist/tools/explain-signal-for-diff.d.ts

@@ -0,0 +1,34 @@
+import { z } from "zod";
+import type { ApiClient } from "../api-client.js";
+export declare const EXPLAIN_SIGNAL_FOR_DIFF_NAME = "zivis_explain_signal_for_my_diff";
+export declare const EXPLAIN_SIGNAL_FOR_DIFF_DESCRIPTION = "Check whether your proposed change would affect a specific SIGNAL.\n\nYou have a SIGNAL flagged in your application's threat model. You're about to make a code change that may or may not address it. Use this tool to see whether your diff touches the files that triggered the signal \u2014 and a heuristic verdict on impact.\n\nReturns:\n  - all_evidence_files \u2014 every file the signal cites\n  - evidence_files_in_diff \u2014 the subset that your proposed change touches\n  - verdict: \"may_resolve\" | \"may_persist\" | \"no_impact\"\n\nThe verdict is a heuristic (file overlap), not a guarantee. Run zivis_review_change for the broader picture, or push and let the canonical extraction confirm.";
+export declare const EXPLAIN_SIGNAL_FOR_DIFF_SCHEMA: {
+    application_id: z.ZodOptional<z.ZodString>;
+    signal_id: z.ZodString;
+    changes: z.ZodArray<z.ZodObject<{
+        file_path: z.ZodString;
+        after_content: z.ZodOptional<z.ZodString>;
+        before_content: z.ZodOptional<z.ZodString>;
+    }, z.core.$strip>>;
+};
+export declare function createExplainSignalForDiffHandler(apiClient: ApiClient): (params: {
+    application_id?: string;
+    signal_id: string;
+    changes: Array<{
+        file_path: string;
+        before_content?: string;
+        after_content?: string;
+    }>;
+}) => Promise<{
+    content: {
+        type: "text";
+        text: string;
+    }[];
+    isError: boolean;
+} | {
+    content: {
+        type: "text";
+        text: string;
+    }[];
+    isError?: undefined;
+}>;

package/dist/tools/explain-signal-for-diff.js

@@ -0,0 +1,75 @@
+import { z } from "zod";
+import { requireApplicationId } from "../resolve-application-id.js";
+import { sanitizeResponse } from "../sanitize.js";
+export const EXPLAIN_SIGNAL_FOR_DIFF_NAME = "zivis_explain_signal_for_my_diff";
+export const EXPLAIN_SIGNAL_FOR_DIFF_DESCRIPTION = `Check whether your proposed change would affect a specific SIGNAL.
+
+You have a SIGNAL flagged in your application's threat model. You're about to make a code change that may or may not address it. Use this tool to see whether your diff touches the files that triggered the signal — and a heuristic verdict on impact.
+
+Returns:
+  - all_evidence_files — every file the signal cites
+  - evidence_files_in_diff — the subset that your proposed change touches
+  - verdict: "may_resolve" | "may_persist" | "no_impact"
+
+The verdict is a heuristic (file overlap), not a guarantee. Run zivis_review_change for the broader picture, or push and let the canonical extraction confirm.`;
+export const EXPLAIN_SIGNAL_FOR_DIFF_SCHEMA = {
+    application_id: z
+        .string()
+        .optional()
+        .describe("Application UUID. If omitted, uses applicationId from .zivis/project.json."),
+    signal_id: z.string().describe("Signal logical id (from zivis_list_signals)"),
+    changes: z
+        .array(z.object({
+        file_path: z.string(),
+        after_content: z.string().optional(),
+        before_content: z.string().optional(),
+    }))
+        .min(1)
+        .describe("Proposed changes"),
+};
+export function createExplainSignalForDiffHandler(apiClient) {
+    return async (params) => {
+        const req = requireApplicationId(params.application_id);
+        if (!req.ok) {
+            return {
+                content: [{ type: "text", text: `Error: ${req.message}` }],
+                isError: true,
+            };
+        }
+        const application_id = req.id;
+        try {
+            const data = await apiClient.post(`/api/apps/${application_id}/signals/${params.signal_id}/explain-for-diff`, {
+                changes: params.changes.map((c) => ({
+                    filePath: c.file_path,
+                    beforeContent: c.before_content,
+                    afterContent: c.after_content,
+                })),
+            });
+            const result = {
+                application_id: data.applicationId,
+                signal_id: data.signalLogicalId,
+                title: data.title,
+                severity: data.severity,
+                verdict: data.verdict,
+                evidence_files_in_diff: data.evidenceFilesInDiff,
+                all_evidence_files: data.allEvidenceFiles,
+                caveats: data.caveats,
+            };
+            return {
+                content: [
+                    {
+                        type: "text",
+                        text: JSON.stringify(sanitizeResponse(result), null, 2),
+                    },
+                ],
+            };
+        }
+        catch (err) {
+            const message = err instanceof Error ? err.message : "Failed to explain signal for diff";
+            return {
+                content: [{ type: "text", text: `Error: ${message}` }],
+                isError: true,
+            };
+        }
+    };
+}

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

@@ -1,9 +1,3 @@
-/**
- * MCP Tool: Generate Diagram from Infrastructure Source
- *
- * Reads a local docker-compose file and sends it to the ZIVIS API
- * for server-side parsing and canvas diagram generation.
- */
 import { z } from "zod";
 import type { ApiClient } from "../api-client.js";
 export declare const GENERATE_DIAGRAM_NAME = "zivis_generate_diagram";

package/dist/tools/generate-diagram.js

@@ -1,13 +1,15 @@
-/**
- * MCP Tool: Generate Diagram from Infrastructure Source
- *
- * Reads a local docker-compose file and sends it to the ZIVIS API
- * for server-side parsing and canvas diagram generation.
- */
 import { z } from "zod";
 import { readFile } from "fs/promises";
-import { join } from "path";
+import { join, relative, resolve } from "path";
 import { sanitizeResponse } from "../sanitize.js";
+function resolveWithinProjectDir(projectDir, candidate) {
+    const base = resolve(projectDir);
+    const target = resolve(base, candidate);
+    const rel = relative(base, target);
+    if (rel.startsWith(".."))
+        return null;
+    return target;
+}
 export const GENERATE_DIAGRAM_NAME = "zivis_generate_diagram";
 export const GENERATE_DIAGRAM_DESCRIPTION = `Generate a visual architecture diagram from a Docker Compose file.
 
@@ -52,13 +54,21 @@ export function createGenerateDiagramHandler(apiClient) {
     return async (params) => {
         const projectDir = params.project_dir || process.cwd();
         const sourceFormat = params.source_format || "docker-compose";
-        // Find and read the compose file
         let filePath = params.file_path;
         let content = null;
         if (filePath) {
-            const resolved = filePath.startsWith("/")
-                ? filePath
-                : join(projectDir, filePath);
+            const resolved = resolveWithinProjectDir(projectDir, filePath);
+            if (!resolved) {
+                return {
+                    content: [
+                        {
+                            type: "text",
+                            text: `Error: file_path must resolve inside project_dir (got: ${filePath})`,
+                        },
+                    ],
+                    isError: true,
+                };
+            }
             try {
                 content = await readFile(resolved, "utf-8");
             }
@@ -82,7 +92,6 @@ export function createGenerateDiagramHandler(apiClient) {
                     break;
                 }
                 catch {
-                    /* continue */
                 }
             }
             if (!content) {
@@ -150,4 +159,3 @@ export function createGenerateDiagramHandler(apiClient) {
         }
     };
 }
-//# sourceMappingURL=generate-diagram.js.map

package/dist/tools/get-application-overview.d.ts

@@ -1,8 +1,3 @@
-/**
- * zivis_get_application_overview — Rich application context with endpoints & threat model
- *
- * Maps to: GET /api/rt/applications/:id/overview
- */
 import { z } from "zod";
 import type { ApiClient } from "../api-client.js";
 export declare const GET_APPLICATION_OVERVIEW_NAME = "zivis_get_application_overview";

package/dist/tools/get-application-overview.js

@@ -1,8 +1,3 @@
-/**
- * zivis_get_application_overview — Rich application context with endpoints & threat model
- *
- * Maps to: GET /api/rt/applications/:id/overview
- */
 import { z } from "zod";
 import { requireApplicationId } from "../resolve-application-id.js";
 import { sanitizeResponse } from "../sanitize.js";
@@ -140,4 +135,3 @@ export function createGetApplicationOverviewHandler(apiClient) {
         }
     };
 }
-//# sourceMappingURL=get-application-overview.js.map

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

@@ -1,8 +1,3 @@
-/**
- * zivis_get_application — Get details of a specific application
- *
- * Maps to: GET /api/rt/applications/:id
- */
 import { z } from "zod";
 import type { ApiClient } from "../api-client.js";
 export declare const GET_APPLICATION_NAME = "zivis_get_application";

package/dist/tools/get-application.js

@@ -1,8 +1,3 @@
-/**
- * zivis_get_application — Get details of a specific application
- *
- * Maps to: GET /api/rt/applications/:id
- */
 import { z } from "zod";
 import { requireApplicationId } from "../resolve-application-id.js";
 import { sanitizeResponse } from "../sanitize.js";
@@ -80,4 +75,3 @@ export function createGetApplicationHandler(apiClient) {
         }
     };
 }
-//# sourceMappingURL=get-application.js.map

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

@@ -1,8 +1,3 @@
-/**
- * zivis_get_diagram — Get full diagram content
- *
- * Maps to: GET /api/diagrams/:id
- */
 import { z } from "zod";
 import type { ApiClient } from "../api-client.js";
 export declare const GET_DIAGRAM_NAME = "zivis_get_diagram";

package/dist/tools/get-diagram.js

@@ -1,8 +1,3 @@
-/**
- * zivis_get_diagram — Get full diagram content
- *
- * Maps to: GET /api/diagrams/:id
- */
 import { z } from "zod";
 import { sanitizeResponse } from "../sanitize.js";
 export const GET_DIAGRAM_NAME = "zivis_get_diagram";
@@ -23,7 +18,6 @@ export function createGetDiagramHandler(apiClient) {
         try {
             const data = await apiClient.get(`/api/diagrams/${params.diagram_id}`);
             const sanitized = sanitizeResponse(data);
-            // Format nodes with clear structure
             const nodes = Array.isArray(sanitized.nodes)
                 ? sanitized.nodes.map((n) => ({
                     node_id: n.id,
@@ -43,7 +37,6 @@ export function createGetDiagramHandler(apiClient) {
                     linked_evidence_ids: n.linkedEvidenceIds || [],
                 }))
                 : [];
-            // Format connections
             const connections = Array.isArray(sanitized.connections)
                 ? sanitized.connections.map((c) => ({
                     connection_id: c.id,
@@ -56,7 +49,6 @@ export function createGetDiagramHandler(apiClient) {
                     metadata: c.metadata || null,
                 }))
                 : [];
-            // Format boundaries
             const boundaries = Array.isArray(sanitized.boundaries)
                 ? sanitized.boundaries.map((b) => ({
                     boundary_id: b.id,
@@ -69,7 +61,6 @@ export function createGetDiagramHandler(apiClient) {
                     height: b.height,
                 }))
                 : [];
-            // Extract linked entity IDs
             const linkedThreatModelIds = Array.isArray(sanitized.threatModelLinks)
                 ? sanitized.threatModelLinks.map((l) => l.threatModelId)
                 : [];
@@ -79,7 +70,7 @@ export function createGetDiagramHandler(apiClient) {
                 description: sanitized.description || null,
                 diagram_type: sanitized.diagramType,
                 content_type: sanitized.contentType,
-                content: sanitized.content || null, // Mermaid source; null for canvas-type diagrams
+                content: sanitized.content || null,
                 source_type: sanitized.sourceType,
                 created_at: sanitized.createdAt,
                 updated_at: sanitized.updatedAt,
@@ -106,4 +97,3 @@ export function createGetDiagramHandler(apiClient) {
         }
     };
 }
-//# sourceMappingURL=get-diagram.js.map

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

@@ -1,8 +1,3 @@
-/**
- * zivis_get_document — Fetch a document by ID, including its full markdown content.
- *
- * Maps to: GET /api/documents/:id
- */
 import { z } from "zod";
 import type { ApiClient } from "../api-client.js";
 export declare const GET_DOCUMENT_NAME = "zivis_get_document";

package/dist/tools/get-document.js

@@ -1,8 +1,3 @@
-/**
- * zivis_get_document — Fetch a document by ID, including its full markdown content.
- *
- * Maps to: GET /api/documents/:id
- */
 import { z } from "zod";
 import { sanitizeResponse } from "../sanitize.js";
 export const GET_DOCUMENT_NAME = "zivis_get_document";
@@ -40,4 +35,3 @@ export function createGetDocumentHandler(apiClient) {
         }
     };
 }
-//# sourceMappingURL=get-document.js.map

package/dist/tools/get-oss-zat.d.ts

@@ -1,8 +1,3 @@
-/**
- * zivis_get_oss_zat — Get the signed attestation token (ZAT) for a GitHub repo
- *
- * Maps to: GET /api/oss-trust/repos/:owner/:repo/zat (public, no auth required)
- */
 import { z } from "zod";
 import type { ZivisConfig } from "../types.js";
 export declare const GET_OSS_ZAT_NAME = "zivis_get_oss_zat";

package/dist/tools/get-oss-zat.js

@@ -1,8 +1,3 @@
-/**
- * zivis_get_oss_zat — Get the signed attestation token (ZAT) for a GitHub repo
- *
- * Maps to: GET /api/oss-trust/repos/:owner/:repo/zat (public, no auth required)
- */
 import { z } from "zod";
 export const GET_OSS_ZAT_NAME = "zivis_get_oss_zat";
 export const GET_OSS_ZAT_DESCRIPTION = `Get the ZIVIS Attestation Token (ZAT) for a GitHub repository — a cryptographically signed, machine-verifiable supply chain credential.
@@ -32,7 +27,6 @@ export const GET_OSS_ZAT_SCHEMA = {
         .string()
         .describe("GitHub repo URL (https://github.com/owner/repo) or owner/repo string"),
 };
-/** Parse GitHub URL or owner/repo into components */
 function parseRepo(input) {
     const trimmed = input.trim();
     const urlMatch = trimmed.match(/^https?:\/\/(?:www\.)?github\.com\/([a-zA-Z0-9._-]+)\/([a-zA-Z0-9._-]+)/);
@@ -102,4 +96,3 @@ export function createGetOssZatHandler(config) {
         }
     };
 }
-//# sourceMappingURL=get-oss-zat.js.map

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

@@ -0,0 +1,24 @@
+import { z } from "zod";
+import type { ApiClient } from "../api-client.js";
+export declare const GET_SIGNAL_NAME = "zivis_get_signal";
+export declare const GET_SIGNAL_DESCRIPTION = "Get full detail on a single Signal by its id.\n\nReturns the qualified narrative \u2014 description, mitigation, attack-chain context, taxonomy (STRIDE / ATPS layer / MITRE / OWASP / compliance mappings), detected safeguards and what breaks them, and the polymorphic source-artifact reference for drilling into the native subsystem.\n\nPass `signal_id` from a `zivis_list_signals` response.\n\nSECURITY: Display-shaped output only. No raw graph data.";
+export declare const GET_SIGNAL_SCHEMA: {
+    application_id: z.ZodOptional<z.ZodString>;
+    signal_id: z.ZodString;
+};
+export declare function createGetSignalHandler(apiClient: ApiClient): (params: {
+    application_id?: string;
+    signal_id: string;
+}) => Promise<{
+    content: {
+        type: "text";
+        text: string;
+    }[];
+    isError: boolean;
+} | {
+    content: {
+        type: "text";
+        text: string;
+    }[];
+    isError?: undefined;
+}>;