strimzi-mcp-server

The server uses `KubernetesClient` which relies on local kubeconfig or in-cluster service accounts, requiring appropriate RBAC permissions for Strimzi custom resources and standard Kubernetes resources (Pods, Secrets, Events). It accesses sensitive information like KafkaUser passwords from Kubernetes Secrets, which is necessary for `get_user_credentials` functionality. Communication occurs over standard I/O (stdio), avoiding direct network listeners and reducing external attack surface. No `eval` or similar dynamic code execution, hardcoded credentials (other than implicit kubeconfig usage), or obfuscation patterns were found. The primary security consideration is ensuring the Kubernetes credentials used by the server have the least privilege necessary for its operations.