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

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.

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

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.

ParameterTypeRequiredDescription
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.

Questions about list_instance_group_managers

What does the list_instance_group_managers tool do? +

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.

What parameters does list_instance_group_managers accept? +

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.

How do I enforce a policy on list_instance_group_managers? +

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.

What risk level is list_instance_group_managers? +

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

Can I rate-limit list_instance_group_managers? +

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.

How do I block list_instance_group_managers completely? +

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.

What MCP server provides list_instance_group_managers? +

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

// 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.