Google Kubernetes Engine MCP server
23 tools · Last check that passed 27 Oct 2026, 01:50 UTC
Google's own remote MCP server for Google Kubernetes Engine gives an agent read access to the clusters, node pools and Kubernetes resources of the Google Cloud projects its sign-in reaches. Once a day, Stackduke connects to it the way any MCP client would, with no account and no sign-in, and lists its tools. It never runs them.
All 23 tools
| Tool | Counted as |
|---|---|
apply_k8s_manifest | Deletes |
cancel_operation | Deletes |
delete_k8s_resource | Deletes |
patch_k8s_resource | Deletes |
update_cluster | Deletes |
update_node_pool | Deletes |
create_cluster | Changes things |
create_node_pool | Changes things |
check_k8s_auth | Said to only read |
describe_k8s_resource | Said to only read |
get_cluster | Said to only read |
get_k8s_cluster_info | Said to only read |
get_k8s_logs | Said to only read |
get_k8s_resource | Said to only read |
get_k8s_rollout_status | Said to only read |
get_k8s_version | Said to only read |
get_node_pool | Said to only read |
get_operation | Said to only read |
list_clusters | Said to only read |
list_k8s_api_resources | Said to only read |
list_k8s_events | Said to only read |
list_node_pools | Said to only read |
list_operations | Said to only read |
The tools the server listed at the last check that passed, at its default address and settings, with no sign-in; an account that signs in, or other settings, may see other tools. What a tool is counted as doing is Stackduke's cautious reading of the server's labels, the tool's name and its description: where they disagree it takes whichever says the tool can do most, so it overcounts on purpose. It does not say the server is safe, and it does not list what a tool cannot do. Descriptions are not shown, because they are written for models and may try to steer them.
Recent checks
13 of the last 13 checks passed
A check passes when the server lists its tools. Checked at https://container.googleapis.com/mcp.
Recent changes
No change seen across the last 13 checks that passed.
From the scan of 27 Oct 2026, 01:52 UTC. "Changed" and "Can do more" count changes from the last 30 days; older ones stay listed here. A change made and undone between two checks is not seen. Every check is in the scanner's public data.
Know when Google Kubernetes Engine's tools change.
One email when Google Kubernetes Engine's official MCP server adds, removes or changes tools, with what changed. Nothing else.
What to watch for
- Its sign-in can ask for the read-write container scope or the broad cloud-platform scope, not only the read-only one. Google's GKE MCP documentation
- Resource configurations and container logs come back to the agent, and text an agent reads can carry instructions for it. OWASP, prompt injection
How to limit it
With Google Kubernetes Engine's own settings, as its documentation describes them. Stackduke has not tested them.
- Sign in with the container.read-only scope, which Google says grants read-only access to your GKE resources. Google's GKE MCP documentation
- Google lists the Kubernetes Engine Cluster Viewer role as giving read-only access, so we recommend giving the agent's identity no more than that. Google's GKE MCP documentation
- Google recommends a separate identity for agents that use MCP tools, so that their access can be controlled and monitored. Google's GKE MCP documentation
What Stackduke is designed to do
Stackduke is designed to sit between your agents and their MCP servers: to check each tool call against your rules before it runs, hold the risky ones for a person to approve, and keep a record of what was decided.
It does not yet forward or block tool calls for customers. Today it reads what this server offers and publishes what changes.