Get GKE server configuration for a specific location.
AI agents call get_gke_server_config to retrieve information from Google Cloud MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves server configuration information, which is a read-only operation with no side effects. However, GKE server configurations may contain sensitive cluster details, default versions, and deployment parameters that could be valuable for reconnaissance or attack planning, warranting medium severity.
From the tool's definition Tool name 'get_gke_server_config' and description 'Get GKE server configuration for a specific location' indicate a retrieval operation that queries GKE configuration data without modifying state.
Attacks that exploit this kind of access
Get GKE server configuration for a specific location. It is categorised as a Read tool in the Google Cloud MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Cloud MCP Server MCP server in PolicyLayer and add a rule for get_gke_server_config: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Google Cloud MCP Server. Nothing to install.
get_gke_server_config is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_gke_server_config rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for get_gke_server_config. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
get_gke_server_config is provided by the Google Cloud MCP Server MCP server (nsachin08/gcpmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →