armis-knowledge-mcp

Produce a structured before/after report after a CWE-fix run against the Armis Knowledge DEV environment. You collect the scanner findings; the server assembles the report — attribution, summary, residuals — and returns finished markdown. Optionally opens a PR. Use after finishing a batch of CWE fixes when the user asks for a report / diff / PR body. Triggers: /cwe-fix-report-dev, generate cwe fix report, report the fixes, cwe report, open a pr for the fixes.

Produce a structured before/after report after a CWE-fix run against the Armis Knowledge PROD environment. You collect the scanner findings; the server assembles the report — attribution, summary, residuals — and returns finished markdown. Optionally opens a PR. Use after finishing a batch of CWE fixes when the user asks for a report / diff / PR body. Triggers: /cwe-fix-report, generate cwe fix report, report the fixes, cwe report, open a pr for the fixes.

Produce a structured before/after report after a CWE-fix run against the Armis Knowledge DEV environment (shell-skills variant). You collect git + scanner findings; the backend assembles the report and returns finished markdown. Optionally opens a PR. Use after finishing a batch of CWE fixes when the user asks for a report / diff / PR body. Triggers: /cwe-fix-report-dev, generate cwe fix report, report the fixes, cwe report, open a pr for the fixes.

Produce a structured before/after report after a CWE-fix run against the Armis Knowledge PROD environment (shell-skills variant). You collect git + scanner findings; the backend assembles the report and returns finished markdown. Optionally opens a PR. Use after finishing a batch of CWE fixes when the user asks for a report / diff / PR body. Triggers: /cwe-fix-report, generate cwe fix report, report the fixes, cwe report, open a pr for the fixes.

Produce a structured before/after report after a CWE-fix run against the Armis Knowledge STAGE environment (shell-skills variant). You collect git + scanner findings; the backend assembles the report and returns finished markdown. Optionally opens a PR. Use after finishing a batch of CWE fixes when the user asks for a report / diff / PR body. Triggers: /cwe-fix-report-stage, generate cwe fix report, report the fixes, cwe report, open a pr for the fixes.

Produce a structured before/after report after a CWE-fix run against the Armis Knowledge STAGE environment. You collect the scanner findings; the server assembles the report — attribution, summary, residuals — and returns finished markdown. Optionally opens a PR. Use after finishing a batch of CWE fixes when the user asks for a report / diff / PR body. Triggers: /cwe-fix-report-stage, generate cwe fix report, report the fixes, cwe report, open a pr for the fixes.

Query the Armis Knowledge base (DEV environment) for organizational standards, policies, and tenant-specific guidance. Use when generating, reviewing, or remediating code so the work matches the organization's standards. Triggers: /knowledge-dev, what are our standards for, what does our org say about, search knowledge, list standards, knowledge base.

Query the Armis Knowledge base (PROD environment) for organizational standards, policies, and tenant-specific guidance. Use when generating, reviewing, or remediating code so the work matches the organization's standards. Triggers: /knowledge, what are our standards for, what does our org say about, search knowledge, list standards, knowledge base.

Query the Armis Knowledge base (DEV) for organizational standards, policies, and tenant-specific guidance. Use when generating, reviewing, or remediating code so the work matches the organization's standards. Triggers: /knowledge-dev, what are our standards for, what does our org say about, search knowledge, list standards.

Query the Armis Knowledge base (PROD) for organizational standards, policies, and tenant-specific guidance. Use when generating, reviewing, or remediating code so the work matches the organization's standards. Triggers: /knowledge, what are our standards for, what does our org say about, search knowledge, list standards.

Query the Armis Knowledge base (STAGE) for organizational standards, policies, and tenant-specific guidance. Use when generating, reviewing, or remediating code so the work matches the organization's standards. Triggers: /knowledge-stage, what are our standards for, what does our org say about, search knowledge, list standards.

Query the Armis Knowledge base (STAGE environment) for organizational standards, policies, and tenant-specific guidance. Use when generating, reviewing, or remediating code so the work matches the organization's standards. Triggers: /knowledge-stage, what are our standards for, what does our org say about, search knowledge, list standards, knowledge base.

Fetch organization-specific remediation guidance for a given CWE from the Armis Knowledge DEV environment. Use when fixing a vulnerability identified by CWE ID, when triaging scanner findings, or when the user asks how to remediate a specific weakness. Triggers: /cwe-fix-dev, how do we fix CWE-, remediation for CWE, false positive CWE, cwe guidance.

Fetch organization-specific guidance for a web framework (Django, Flask, FastAPI, Express, Rails, Spring, etc.) from the Armis Knowledge DEV environment. Use when generating or reviewing code that uses a specific framework. Triggers: /framework-guidance-dev, how do we use Django, Flask conventions, our patterns for Express, framework standards.

Fetch organization-specific guidance for a programming language or runtime (Python, Go, TypeScript, Java, Rust, Node, etc.) from the Armis Knowledge DEV environment. Use when generating or reviewing code in a specific language. Triggers: /tech-guidance-dev, how do we write Python, Go conventions, our TypeScript patterns, language standards.

Fetch organization-specific remediation guidance for a given CWE from the Armis Knowledge PROD environment. Use when fixing a vulnerability identified by CWE ID, when triaging scanner findings, or when the user asks how to remediate a specific weakness. Triggers: /cwe-fix, how do we fix CWE-, remediation for CWE, false positive CWE, cwe guidance.

Fetch organization-specific guidance for a web framework (Django, Flask, FastAPI, Express, Rails, Spring, etc.) from the Armis Knowledge PROD environment. Use when generating or reviewing code that uses a specific framework. Triggers: /framework-guidance, how do we use Django, Flask conventions, our patterns for Express, framework standards.

Fetch organization-specific guidance for a programming language or runtime (Python, Go, TypeScript, Java, Rust, Node, etc.) from the Armis Knowledge PROD environment. Use when generating or reviewing code in a specific language. Triggers: /tech-guidance, how do we write Python, Go conventions, our TypeScript patterns, language standards.

Fetch organization-specific remediation guidance for a given CWE from the Armis Knowledge STAGE environment. Use when fixing a vulnerability identified by CWE ID, when triaging scanner findings, or when the user asks how to remediate a specific weakness. Triggers: /cwe-fix-stage, how do we fix CWE-, remediation for CWE, false positive CWE, cwe guidance.

Fetch organization-specific guidance for a web framework (Django, Flask, FastAPI, Express, Rails, Spring, etc.) from the Armis Knowledge STAGE environment. Use when generating or reviewing code that uses a specific framework. Triggers: /framework-guidance-stage, how do we use Django, Flask conventions, our patterns for Express, framework standards.

Fetch organization-specific guidance for a programming language or runtime (Python, Go, TypeScript, Java, Rust, Node, etc.) from the Armis Knowledge STAGE environment. Use when generating or reviewing code in a specific language. Triggers: /tech-guidance-stage, how do we write Python, Go conventions, our TypeScript patterns, language standards.

Fetch organization-specific remediation guidance for a given CWE from the Armis Knowledge DEV environment. Use when fixing a vulnerability identified by CWE ID, when triaging scanner findings, or when the user asks how to remediate a specific weakness. Also surfaces false-positive patterns. Triggers: /cwe-fix-dev, how do we fix CWE-, remediation for CWE, false positive CWE, cwe guidance.

Fetch organization-specific remediation guidance for a given CWE from the Armis Knowledge PROD environment. Use when fixing a vulnerability identified by CWE ID, when triaging scanner findings, or when the user asks how to remediate a specific weakness. Also surfaces false-positive patterns. Triggers: /cwe-fix, how do we fix CWE-, remediation for CWE, false positive CWE, cwe guidance.

Fetch organization-specific remediation guidance for a given CWE from the Armis Knowledge STAGE environment. Use when fixing a vulnerability identified by CWE ID, when triaging scanner findings, or when the user asks how to remediate a specific weakness. Also surfaces false-positive patterns. Triggers: /cwe-fix-stage, how do we fix CWE-, remediation for CWE, false positive CWE, cwe guidance.

Ask a free-form question about the Armis Knowledge base (PROD) and get a synthesized answer with citations. Use for explanatory questions about documents ("what does X policy say?", "summarize our position on Y"). Do NOT use for code generation or review — call /knowledge for those so the calling agent stays in control of how standards are applied. Triggers: /ask, /ask-knowledge, ask the knowledge base, what does our knowledge say about, summarize what we have on.

Fetch organization-specific guidance for a web framework (Django, Flask, FastAPI, Express, Rails, Spring, etc.) from the Armis Knowledge PROD environment. Use when generating or reviewing code that uses a specific framework, so framework-specific patterns and pitfalls are applied. Triggers: /framework-guidance, how do we use Django, Flask conventions, our patterns for Express, framework standards.

Fetch organization-specific guidance for a programming language or runtime (Python, Go, TypeScript, Java, Rust, Node, etc.) from the Armis Knowledge PROD environment. Use when generating or reviewing code in a specific language so language idioms, banned APIs, and required patterns are applied. Triggers: /tech-guidance, how do we write Python, Go conventions, our TypeScript patterns, language standards.

Ask a free-form question about the Armis Knowledge base (STAGE) and get a synthesized answer with citations. Use for explanatory questions about documents ("what does X policy say?", "summarize our position on Y"). Do NOT use for code generation or review — call /knowledge-stage for those so the calling agent stays in control of how standards are applied. Triggers: /ask-stage, /ask-knowledge-stage, ask the knowledge base, what does our knowledge say about, summarize what we have on.

Fetch organization-specific guidance for a web framework (Django, Flask, FastAPI, Express, Rails, Spring, etc.) from the Armis Knowledge STAGE environment. Use when generating or reviewing code that uses a specific framework, so framework-specific patterns and pitfalls are applied. Triggers: /framework-guidance-stage, how do we use Django, Flask conventions, our patterns for Express, framework standards.

Fetch organization-specific guidance for a programming language or runtime (Python, Go, TypeScript, Java, Rust, Node, etc.) from the Armis Knowledge STAGE environment. Use when generating or reviewing code in a specific language so language idioms, banned APIs, and required patterns are applied. Triggers: /tech-guidance-stage, how do we write Python, Go conventions, our TypeScript patterns, language standards.

Ask a free-form question about the Armis Knowledge base (DEV) and get a synthesized answer with citations. Use for explanatory questions about documents ("what does X policy say?", "summarize our position on Y"). Do NOT use for code generation or review — call /knowledge-dev for those so the calling agent stays in control of how standards are applied. Triggers: /ask-dev, /ask-knowledge-dev, ask the knowledge base, what does our knowledge say about, summarize what we have on.

Fetch organization-specific guidance for a web framework (Django, Flask, FastAPI, Express, Rails, Spring, etc.) from the Armis Knowledge DEV environment. Use when generating or reviewing code that uses a specific framework, so framework-specific patterns and pitfalls are applied. Triggers: /framework-guidance-dev, how do we use Django, Flask conventions, our patterns for Express, framework standards.

Fetch organization-specific guidance for a programming language or runtime (Python, Go, TypeScript, Java, Rust, Node, etc.) from the Armis Knowledge DEV environment. Use when generating or reviewing code in a specific language so language idioms, banned APIs, and required patterns are applied. Triggers: /tech-guidance-dev, how do we write Python, Go conventions, our TypeScript patterns, language standards.