// MCP TOOL REFERENCE

DEVOPS TOOLS

11 tools from the Devops MCP Server, categorised by risk level.

READ TOOLS

k8s__describe_resource Full describe for any resource type k8s__get_events Cluster or namespace events, filterable by reason k8s__get_pod_logs Get logs from a pod container k8s__get_resource_usage CPU/mem usage per pod via metrics-server k8s__list_contexts All kubeconfig contexts and the active one k8s__list_deployments Deployments with replica counts and rollout health k8s__list_pods List pods with status, restarts, node, and age

WRITE TOOLS

k8s__switch_context Switch active context (session-scoped)

DESTRUCTIVE TOOLS

k8s__delete_resource Delete a named resource — requires confirm: true

EXECUTE TOOLS

k8s__rollout_restart Trigger rolling restart of a deployment k8s__scale_deployment Scale replicas with dry-run diff preview

// FAQ

How many tools does the Devops MCP server have? +

The Devops MCP server exposes 11 tools across 4 categories: Read, Write, Destructive, Execute.

How do I enforce policies on Devops tools? +

Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Devops server.

What risk categories do Devops tools fall into? +

Devops tools are categorised as Read (7), Write (1), Destructive (1), Execute (2). Each category has a recommended default policy.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

GET STARTED →