list_instance_attached_disks

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/list-instance-attached-disks.md

WHAT IT DOES

What list_instance_attached_disks does on Mcp

AI agents call list_instance_attached_disks 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. The instance name.
`zone`	string	Yes	Required. The zone of the instance.
`project`	string	Yes	Required. Project ID for this request.

Parameters from the server's own tool schema.

RISK

Why list_instance_attached_disks is rated Low

This tool performs a read-only query of infrastructure metadata. It retrieves and lists configuration details about attached disks but does not modify, delete, execute, or create any resources. The blast radius of misuse is minimal—an agent with this tool can only view disk information it already has authorization to access. Appropriate for Read category with low severity.

From the tool's definition The tool 'Lists the disks attached to a Compute Engine virtual machine' and returns details such as 'kind, type, mode, saved state, source, device name, index, boot, initialize parameters, auto delete, licenses, interface, guest OS features, disk encryption…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_instance_attached_disks 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_attached_disks, this is the rule to start with:

list_instance_attached_disks Allowed

list_instance_attached_disks is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_instance_attached_disks": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every list_instance_attached_disks call is checked against it from then on.

FAQ

Questions about list_instance_attached_disks

What does the list_instance_attached_disks tool do? +

Lists the disks attached to a Compute Engine virtual machine (VM) instance. For each attached disk, the response includes details such as kind, type, mode, saved state, source, device name, index, boot, initialize parameters, auto delete, licenses,, interface, guest OS features, disk encryption key, disk size, shielded instance initial state, force attach, and architecture. Requires project, zone, and instance 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 list_instance_attached_disks accept? +

list_instance_attached_disks 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 list_instance_attached_disks? +

Register the MCP server in PolicyLayer and add a rule for list_instance_attached_disks: 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_attached_disks? +

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

Can I rate-limit list_instance_attached_disks? +

Yes. Add a rate_limit block to the list_instance_attached_disks 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_attached_disks completely? +

Set action: deny in the PolicyLayer policy for list_instance_attached_disks. 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_attached_disks? +

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

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 29 tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →