Blekline governs agent interaction at the MCP, SDK, ingress, and sidecar boundary. Not every client surface receives the same enforcement depth. Use this page in procurement, pilot scoping, and NHIM gap reviews.
Two scopes, one policy
| Scope | Where | Enforcement |
|---|---|---|
| Laptop / VDI | Cursor, Claude Code, VS Code | Local hooks, stdio MCP, optional browser extension |
| Cluster | Kubernetes / OpenShift agent pods | Admission inject, sidecar mandatory hop, NetworkPolicy |
Workspace policy is shared; runtime log events label which scope produced each event.
Coverage matrix
| Surface | Scope | Notes |
|---|---|---|
| MCP tool calls via sidecar / ingress proxy | In scope | Mask and tool-args evaluate at the mandatory hop |
| Kubernetes admission Auto-Route | In scope | Sidecar env on annotated agent workloads |
| Mandatory-hop NetworkPolicy | In scope | Agent egress via sidecar when enforce profile is applied |
| Cursor / Claude Code local hooks | Partial | Laptop scope — separate from cluster agents |
| Windows IDE hosts | Out of scope | Hooks-only; no kernel or sidecar enforce on Windows |
| QUIC / non-TCP egress | Out of scope | Not in sidecar socket filter scope — document in NHIM audit |
| Native IDE chat without ingress | Out of scope | Requires hooks or routing chat through governed ingress |
| eBPF kernel plane (Enterprise) | Partial | Socket/exec metadata — not TLS plaintext |
Hosted /api/mask on Fleet / Enterprise | Out of scope | Production masking runs in-cluster via sidecar |
In-app matrix: Operations → Coverage (Fleet and in-VPC shells).
Windows & hooks-only honesty
Browser extension and Windows Cursor hosts are hooks-only. They do not receive cluster NetworkPolicy or sidecar enforcement. Regulated agent workloads should pair laptop hooks with cluster scope for production agents.
NHIM audit alignment
Static NHIM rules (NHIM-014 wide HTTPS egress, hostNetwork, etc.) map to residuals above. Upload audit JSON in Deployment hub before enforce activation.