What problem does it solve?
Kubernetes is default-allow, so a namespace with no NetworkPolicy permits all traffic — and read-only queries can silently return incomplete results when permissions are insufficient. This Skill audits cluster network segmentation correctly, distinguishing "no policies exist" from "policies could not be seen" so security reviews are not based on false negatives.
Core Features & Use Cases
- Scoped NetworkPolicy Audits: Lists NetworkPolicies cluster-wide or per-namespace via a read-only k8s-mcp server, reporting podSelectors, policyTypes, and ingress/egress rules rather than just policy existence.
- Permission Preflight: Verifies cluster-wide list permission with
kubectl auth can-i before trusting empty results, preventing audit lies caused by silent namespace-scoped fallback.
- Six-Cause Empty-Result Diagnosis: Distinguishes permission gaps, missing namespaces, empty namespaces, selector typos, missing CRDs (Cilium/Calico), and unreachable clusters.
- Use Case: During a security review, ask what can reach a production pod and receive the applicable policies, the exact scope queried, which cluster answered, and an explicit statement of what is permitted.
Quick Start
Ask the agent to review which NetworkPolicies apply to the payments namespace and state what traffic is permitted to those pods.