list_instance_templates
Lists Compute Engine instance templates. Details for each instance template include name, ID, description, machine type, region, and creation timestamp. Requires project as input.
This record as markdown: /tools/com-googleapis-compute-mcp/list-instance-templates.md
What list_instance_templates does on Mcp
AI agents call list_instance_templates 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 instance templates to return. |
pageToken | string | — | Optional. A page token received from a previous call to list instance templates. |
Parameters from the server's own tool schema.
Why list_instance_templates is rated Low
This tool retrieves and queries metadata about infrastructure templates without side effects. It requires only a project identifier as input and returns informational data. Classification as Read is appropriate; severity is low as misuse would only expose metadata about instance templates, not directly compromise running infrastructure or enable destructive actions without additional tools.
From the tool's definition Tool name and description both indicate a list/query operation: 'Lists Compute Engine instance templates' with read-only outputs (name, ID, description, machine type, region, creation timestamp). No mutation, deletion, or execution of infrastructure changes.
Attacks that exploit this kind of access
The rule that runs list_instance_templates 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_instance_templates, this is the rule to start with:
list_instance_templates 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_instance_templates call is checked against it from then on.
Questions about list_instance_templates
Lists Compute Engine instance templates. Details for each instance template include name, ID, description, machine type, region, 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_instance_templates 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_instance_templates: 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_instance_templates 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_instance_templates 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_instance_templates. 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_instance_templates 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