get_zone_operation
Get details of a zone operation, including its id, name, status, creation timestamp, error, warning, HTTP error message and HTTP error status code. Requires project, zone, and operation name as input.
This record as markdown: /tools/com-googleapis-compute-mcp/get-zone-operation.md
What get_zone_operation does on Mcp
AI agents call get_zone_operation 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 |
|---|---|---|---|
name | string | Yes | Required. Identifier. The operation name. |
zone | string | Yes | Required. The zone of the operation. |
project | string | Yes | Required. Project ID for this request. |
Parameters from the server's own tool schema.
Why get_zone_operation is rated Low
This tool queries and retrieves information about an existing zone operation without modifying, deleting, or executing any infrastructure changes. It is purely informational and has no blast radius beyond exposing potentially sensitive operational metadata.
From the tool's definition Tool name is 'get_zone_operation' and description states it retrieves details of a zone operation including 'id, name, status, creation timestamp, error, warning, HTTP error message and HTTP error status code.' The verb 'Get' and the action of retrieving…
Attacks that exploit this kind of access
The rule that runs get_zone_operation 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 get_zone_operation, this is the rule to start with:
get_zone_operation 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 get_zone_operation call is checked against it from then on.
Questions about get_zone_operation
Get details of a zone operation, including its id, name, status, creation timestamp, error, warning, HTTP error message and HTTP error status code. Requires project, zone, and operation name as input. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
get_zone_operation accepts 3 parameters: name, zone, project. Required: name, zone, project. 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 get_zone_operation: 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.
get_zone_operation 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_zone_operation 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_zone_operation. 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_zone_operation is provided by the MCP server (https://compute.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