get_instance_template_properties
Get instance properties of a Compute Engine instance template. This includes properties such as description, tags, machine type, network interfaces, disks, metadata, service accounts, scheduling options, labels, guest accelerators, reservation affinity, and shielded/confidential instance configur...
This record as markdown: /tools/com-googleapis-compute-mcp/get-instance-template-properties.md
What get_instance_template_properties does on Mcp
AI agents call get_instance_template_properties 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. Name of the instance template to return. |
project | string | Yes | Required. Project ID for this request. |
Parameters from the server's own tool schema.
Why get_instance_template_properties is rated Low
This tool retrieves metadata and configuration information about a Compute Engine instance template. It performs a read-only query operation with no side effects—it does not create, modify, delete, or execute any infrastructure changes.
From the tool's definition Tool name contains 'get_' and description states it 'Get[s] instance properties' and 'Requires project and instance template name as input' with no mention of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs get_instance_template_properties 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_instance_template_properties, this is the rule to start with:
get_instance_template_properties 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_instance_template_properties call is checked against it from then on.
Questions about get_instance_template_properties
Get instance properties of a Compute Engine instance template. This includes properties such as description, tags, machine type, network interfaces, disks, metadata, service accounts, scheduling options, labels, guest accelerators, reservation affinity, and shielded/confidential instance configurations. Requires project and instance template name as input. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
get_instance_template_properties accepts 2 parameters: name, project. Required: name, 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_instance_template_properties: 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_instance_template_properties 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_instance_template_properties 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_instance_template_properties. 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_instance_template_properties 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