Sysdig MCP Server

The design detail worth copying is that the advertised tool list is not fixed. On each request the server checks what the supplied API token is allowed to do and hides the tools it cannot serve, so a token without metrics read access never puts those calls in front of the model and the agent cannot propose an action that would come back denied. Coverage is Kubernetes-shaped: clusters, nodes, workloads by desired, ready, running or unavailable state, pod containers, cronjobs, running pod counts grouped by cluster and namespace, and a ranked view of the pods with the most unready replicas. Sysdig has split its Secure runtime-event tools into a separate package, so this one stays a monitoring surface.