fleet-mcp

The server acts as a powerful gateway to Kubernetes, requiring a Rancher bearer token ('R_token' header) with potentially broad RBAC permissions for its operations. This means the server operates with the permissions of the provided token; therefore, securing the token and limiting its scope is critical. While TLS is supported, the local development setup allows 'INSECURE_SKIP_TLS=true', which should not be used in production. The Kubernetes deployment manifest includes extensive ClusterRole permissions (full CRUD for many Fleet resources), which should be reviewed and potentially restricted based on specific use cases. There are no obvious code execution vulnerabilities like 'eval' or hardcoded secrets.