list_images
Lists Compute Engine Images. Details for each image include name, ID, status, family, and creation timestamp. Requires project as input.
This record as markdown: /tools/com-googleapis-compute-mcp/list-images.md
What list_images does on Mcp
AI agents call list_images 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 |
|---|---|---|---|
project | string | Yes | Required. Project ID for this request. |
pageSize | integer | — | Optional. The maximum number of images to return. |
pageToken | string | — | Optional. A page token received from a previous call to list images. |
Parameters from the server's own tool schema.
Why list_images is rated Low
This tool retrieves and queries image metadata from a cloud infrastructure system without creating, modifying, deleting, or executing operations. It is a read-only list operation that returns descriptive information only. The presence of destructive tools (delete_instance) and write tools (create_instance) on the same server does not elevate this tool's classification.
From the tool's definition Tool description states it 'Lists Compute Engine Images' and returns 'name, ID, status, family, and creation timestamp' — purely informational retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs list_images 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_images, this is the rule to start with:
list_images 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_images call is checked against it from then on.
Questions about list_images
Lists Compute Engine Images. Details for each image include name, ID, status, family, and creation timestamp. Requires project as input. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
list_images accepts 3 parameters: project, pageSize, pageToken. Required: 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_images: 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_images 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_images 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_images. 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_images 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