list_operations
Lists GKE operations in a given project and location. Location can be a region, zone, or '-' for all locations.
This record as markdown: /tools/com-googleapis-container-mcp/list-operations.md
What list_operations does on Mcp
AI agents call list_operations to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
parent | string | Yes | Required. The parent (project and location) where the operations will be listed. Specified in the format `projects/*/locations/*`. Location "-" matches all zone |
Parameters from the server's own tool schema.
Why list_operations is rated Low
list_operations retrieves and queries existing GKE operations without creating, modifying, deleting, or executing any infrastructure changes. This is a straightforward informational/diagnostic tool with minimal blast radius if misused by an agent—it only exposes metadata about operations that have already occurred or are in progress.
From the tool's definition Tool description states 'Lists GKE operations' — a retrieval operation with no modification or side effects. The word 'list' and 'read access' in the server description confirm this is a query-only function.
Attacks that exploit this kind of access
The rule that runs list_operations safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_operations, this is the rule to start with:
list_operations is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every list_operations call is checked against it from then on.
Questions about list_operations
Lists GKE operations in a given project and location. Location can be a region, zone, or '-' for all locations. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
list_operations accepts 1 parameter: parent. Required: parent. The full parameter table on this page comes from the server's own tool schema.
Register the MCP server in PolicyLayer and add a rule for list_operations: 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 Mcp. Nothing to install.
list_operations 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 list_operations 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 list_operations. 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.
list_operations is provided by the MCP server (https://container.googleapis.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue