mcp-for-argo-workflows

The server provides extensive control over Kubernetes Argo Workflows, including create, update, and delete operations. The default Kubernetes RBAC configuration grants a 'ClusterRole' with broad permissions (full CRUD on Argo Workflows resources, plus get/list/watch on pods/logs/events), making it a high-privilege target. If deployed with HTTP/SSE transport, the documentation explicitly states that external authentication middleware is required for production, implying no built-in client authentication. The code itself employs good practices like strict YAML unmarshaling and manifest size limits (1MiB) to prevent certain vulnerabilities, but the overall security posture heavily relies on secure deployment practices and external access controls.