Topic hub

Agent and MCP security.

Agent and MCP security on Kubernetes is the control plane around tool-using systems: mcp security best practices for identity and egress, the owasp top 10 agentic applications mapped to cluster controls, and an ai agent audit trail for every tool call.

01

Coverage

What this hub covers.

Securing AI agents and MCP servers on Kubernetes: OWASP Agentic Top 10 controls, fail-closed tool-call gates, identity, egress and audit trails.

Pre-execution tool-call gate and pinned capability catalog.

Workload identity and no token passthrough.

Egress control and sandboxing for tool execution.

Approvals bound to exact arguments.

Audit trail per tool call.

02

Guides

Related guides.

03

Related cases

Evidence nearby.

Case 27 · Flagship

Agent Security Contract

  • CLI
  • Action
  • Policy

Agent and MCP stacks expand the attack surface beyond prompt text: tool misuse, poisoned tool descriptions, argument injection, and unapproved high-impact actions run without a pre-execution gate

0 false-ALLOW · 0 false-BLOCK on this corpus

Case 15 · Pattern

Policy as Code Guardrails

  • OPA
  • Feedback
  • Promote

Security and platform rules are often discovered only after deployment or during reviews

Standards enforced in CI, not slides

Case 23

Zero Trust Service Mesh

  • Identity
  • mTLS
  • AuthZ

Internal traffic is often trusted by default, making lateral movement and policy gaps hard to see

East-west mTLS by default

Case 19 · Flagship

AI Runtime Platform

  • Python
  • vLLM
  • KServe

AI workloads often start as API calls but become production systems that need identity, policy, scaling, telemetry, and clear ownership

Every model call: policy + trace + budget

04

Related hubs

Nearby topics.

Available for meaningful infrastructure conversations

Build systems that stay calm under pressure.

Available for conversations

Talk infrastructure

Book a working session

Meet ↗

Evidence first

For deep dives

Explore the systems

All cases ↗