mcp-server

The server's Kubernetes deployment uses good container security practices (runAsNonRoot, readOnlyRootFilesystem, drop all capabilities, no privilege escalation). However, the `ClusterRole` associated with the server grants extensive permissions, including `create`, `update`, `patch`, `delete` on all Tekton Pipeline resources (Pipelines, Tasks, PipelineRuns, TaskRuns, StepActions) and `get`, `list`, `watch` on core Kubernetes resources such as `pods`, `namespaces`, `configmaps`, and critically, `secrets`. This broad access is inherent to the server's function of managing Tekton resources, but it means a compromised MCP server would have significant control over the Tekton CI/CD system and read access to sensitive cluster information.