list_instance_group_managers
Lists Compute Engine managed instance groups (MIGs). Details for each MIG include name, ID, instance template, base instance name, target size, target stopped size, target suspended size, status and creation timestamp. Requires project and zone as input.
This record as markdown: /tools/com-googleapis-compute-mcp/list-instance-group-managers.md
What list_instance_group_managers does on Mcp
AI agents call list_instance_group_managers 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 |
|---|---|---|---|
zone | string | Yes | Required. The zone of the instance group managers. |
project | string | Yes | Required. Project ID for this request. |
pageSize | integer | — | Optional. The maximum number of instance group managers to return. |
pageToken | string | — | Optional. A page token received from a previous call to list instance group managers. |
Parameters from the server's own tool schema.
Why list_instance_group_managers is rated Low
This tool retrieves and queries infrastructure metadata without creating, modifying, deleting, or executing any operations. It is a purely informational API call that reads existing resource state. The blast radius of misuse is minimal—an agent could only gather information about existing MIGs, not alter or delete them.
From the tool's definition Tool description states it 'Lists Compute Engine managed instance groups' and returns details like name, ID, instance template, base instance name, target size, status and creation timestamp.
Attacks that exploit this kind of access
The rule that runs list_instance_group_managers 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_group_managers, this is the rule to start with:
list_instance_group_managers 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_group_managers call is checked against it from then on.
Questions about list_instance_group_managers
Lists Compute Engine managed instance groups (MIGs). Details for each MIG include name, ID, instance template, base instance name, target size, target stopped size, target suspended size, status and creation timestamp. Requires project and zone as input. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
list_instance_group_managers accepts 4 parameters: zone, project, pageSize, pageToken. Required: zone, 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_group_managers: 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_group_managers 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_group_managers 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_group_managers. 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_group_managers 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