New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_reservation_details

Get Compute Engine reservation details. Returns reservation details including name, ID, status, creation timestamp, specific reservation properties like machine type, guest accelerators and local SSDs, aggregate reservation properties like VM family and reserved resources, commitment and linked c...

SERVERMcp SOURCEhttps://compute.googleapis.com/mcp
Low RISK CLASS
Category Read
Parameters 33 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-googleapis-compute-mcp/get-reservation-details.md

What get_reservation_details does on Mcp

AI agents call get_reservation_details 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.

ParameterTypeRequiredDescription
name string Yes Required. Identifier. Name of the reservation to retrieve.
zone string Yes Required. The zone of the reservation.
project string Yes Required. Project ID for this request.

Parameters from the server's own tool schema.

Why get_reservation_details is rated Low

This tool purely queries and retrieves existing reservation metadata without creating, modifying, or deleting resources. The verb 'Get' and passive 'Returns' indicate a read-only operation. The required inputs (project, zone, reservation name) are lookup parameters, not configuration changes. Blast radius is minimal—misuse would only expose infrastructure information already owned by the project.

From the tool's definition Tool description uses 'Get' and 'Returns reservation details' with no modifications, deletions, or side effects mentioned. It retrieves information about Compute Engine reservations including name, ID, status, timestamps, and configuration properties.

Questions about get_reservation_details

What does the get_reservation_details tool do? +

Get Compute Engine reservation details. Returns reservation details including name, ID, status, creation timestamp, specific reservation properties like machine type, guest accelerators and local SSDs, aggregate reservation properties like VM family and reserved resources, commitment and linked commitments, sharing settings, and resource status. Requires project, zone, and reservation name as input. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.

What parameters does get_reservation_details accept? +

get_reservation_details accepts 3 parameters: name, zone, project. Required: name, zone, project. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_reservation_details? +

Register the MCP server in PolicyLayer and add a rule for get_reservation_details: 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.

What risk level is get_reservation_details? +

get_reservation_details is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_reservation_details? +

Yes. Add a rate_limit block to the get_reservation_details 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.

How do I block get_reservation_details completely? +

Set action: deny in the PolicyLayer policy for get_reservation_details. 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.

What MCP server provides get_reservation_details? +

get_reservation_details 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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of 's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.