list_commitment_reservations
Lists reservations for a Compute Engine Commitment. 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 ...
This record as markdown: /tools/com-googleapis-compute-mcp/list-commitment-reservations.md
What list_commitment_reservations does on Mcp
AI agents call list_commitment_reservations 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 commitment to look up reservations for. |
region | string | Yes | Required. The region of the commitment. |
project | string | Yes | Required. Project ID for this request. |
Parameters from the server's own tool schema.
Why list_commitment_reservations is rated Low
This tool performs a read-only operation that retrieves infrastructure metadata. It queries and returns reservation details without creating, modifying, or deleting any resources. The blast radius of misuse is minimal — an agent could enumerate reservations and leak information, but cannot alter infrastructure or financial commitments.
From the tool's definition Tool name contains 'list' and description states 'Lists reservations' and 'Returns reservation details' — these are query operations with no modification or deletion. The tool only retrieves and returns existing data about Compute Engine Commitments.
Attacks that exploit this kind of access
The rule that runs list_commitment_reservations 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_commitment_reservations, this is the rule to start with:
list_commitment_reservations 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_commitment_reservations call is checked against it from then on.
Questions about list_commitment_reservations
Lists reservations for a Compute Engine Commitment. 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, region, and commitment name as input. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
list_commitment_reservations accepts 3 parameters: name, region, project. Required: name, region, 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_commitment_reservations: 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_commitment_reservations 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_commitment_reservations 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_commitment_reservations. 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_commitment_reservations 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