list_commitments
Lists Compute Engine Commitments in a region. Details for each commitment include name, ID, status, plan, type, resources, and creation, start and end timestamps. Requires project and region as input.
This record as markdown: /tools/com-googleapis-compute-mcp/list-commitments.md
What list_commitments does on Mcp
AI agents call list_commitments 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 |
|---|---|---|---|
region | string | Yes | Required. The region of the commitments. |
project | string | Yes | Required. Project ID for this request. |
pageSize | integer | — | Optional. The maximum number of commitments to return. |
pageToken | string | — | Optional. A page token received from a previous call to list commitments. |
Parameters from the server's own tool schema.
Why list_commitments is rated Low
This tool retrieves and queries infrastructure commitment metadata from a specific region without performing any side effects, modifications, or destructive actions. It is a straightforward read operation that returns information about existing commitments. The blast radius of misuse is limited to information disclosure about committed resources and billing terms, which is low severity.
From the tool's definition Tool name is 'list_commitments' and description states it 'Lists Compute Engine Commitments' and provides 'Details for each commitment'. The verb 'Lists' and 'Details' indicate retrieval/query operations with no modification or deletion of data.
Attacks that exploit this kind of access
The rule that runs list_commitments 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_commitments, this is the rule to start with:
list_commitments 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_commitments call is checked against it from then on.
Questions about list_commitments
Lists Compute Engine Commitments in a region. Details for each commitment include name, ID, status, plan, type, resources, and creation, start and end timestamps. Requires project and region as input. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
list_commitments accepts 4 parameters: region, project, pageSize, pageToken. Required: 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_commitments: 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_commitments 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_commitments 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_commitments. 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_commitments 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