poly-k8s-mcp

The server explicitly requires Deno's `--allow-run` permission to execute external CLI commands (kubectl, helm, kustomize). This means an MCP client (e.g., an AI assistant) can perform any action that the user running the server can, using their configured kubeconfig and credentials. There are no additional authentication layers between the MCP client and the underlying CLIs. The README explicitly warns that the security boundary is the local kubectl/helm/kustomize configuration. While there are no hardcoded secrets, 'eval' usage, or obvious malicious patterns in the provided source code, the inherent functionality grants significant control over Kubernetes clusters. Users must ensure proper RBAC is configured for the kubeconfig used by the server. The `--allow-net` permission is also granted, which could allow arbitrary network requests, although the provided code mainly focuses on spawning local CLI processes.