list_disks
Lists Compute Engine disks. Details for each disk include name, ID, description, creation timestamp, size, type, status, last attach timestamp, and last detach timestamp. Requires project and zone as input.
This record as markdown: /tools/com-googleapis-compute-mcp/list-disks.md
What list_disks does on Mcp
AI agents call list_disks 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 |
|---|---|---|---|
zone | string | Yes | Required. The zone of the disks to list. |
project | string | Yes | Required. Project ID for this request. |
pageSize | integer | — | Optional. The maximum number of results per page that should be returned. |
pageToken | string | — | Optional. The page token received from the previous call. |
Parameters from the server's own tool schema.
Why list_disks is rated Low
The tool retrieves and queries disk metadata without modifying, deleting, or executing operations. It has no side effects and is a standard read operation. Low severity due to the limited sensitivity of the returned metadata (disk properties rather than encrypted data or secrets), and the broad context of infrastructure management where disk inventory queries are routine operations.
From the tool's definition Tool description states it 'Lists Compute Engine disks' and 'Details for each disk include name, ID, description, creation timestamp, size, type, status, last attach timestamp, and last detach timestamp.' This is purely a retrieval/query operation with no…
Attacks that exploit this kind of access
The rule that runs list_disks 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_disks, this is the rule to start with:
list_disks 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_disks call is checked against it from then on.
Questions about list_disks
Lists Compute Engine disks. Details for each disk include name, ID, description, creation timestamp, size, type, status, last attach timestamp, and last detach timestamp. Requires project and zone as input. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
list_disks accepts 4 parameters: zone, project, pageSize, pageToken. Required: 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 list_disks: 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_disks 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_disks 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_disks. 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_disks 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