list_machine_types
Lists the available Google Compute Engine machine types. Requires project and zone as input. Returns machine types, including id, creationTimestamp, name, description, guest cpus, memory, image space, maximum persistent disks, maximum persisten disks size, deprecated, zone, is shared cpu, acceler...
This record as markdown: /tools/com-googleapis-compute-mcp/list-machine-types.md
What list_machine_types does on Mcp
AI agents call list_machine_types 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 machine types. |
project | string | Yes | Required. Project ID for this request. |
Parameters from the server's own tool schema.
Why list_machine_types is rated Low
This tool retrieves and queries infrastructure metadata (available machine types and their specifications) without side effects. It is a pure read operation that returns static or reference data about available compute resources. The context of sibling tools (create_instance, delete_instance) that perform write/destructive operations further confirms this is informational only.
From the tool's definition Tool performs a 'list' operation that 'Lists the available Google Compute Engine machine types' and 'Returns machine types' with descriptive metadata. No modification, deletion, or execution of operations is performed.
Attacks that exploit this kind of access
The rule that runs list_machine_types 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_machine_types, this is the rule to start with:
list_machine_types 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_machine_types call is checked against it from then on.
Questions about list_machine_types
Lists the available Google Compute Engine machine types. Requires project and zone as input. Returns machine types, including id, creationTimestamp, name, description, guest cpus, memory, image space, maximum persistent disks, maximum persisten disks size, deprecated, zone, is shared cpu, accelerators, and architecture. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
list_machine_types accepts 2 parameters: zone, project. 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_machine_types: 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_machine_types 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_machine_types 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_machine_types. 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_machine_types 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