get_disk_performance_config
Get performance configuration of a Compute Engine disk, including its type, size, provisioned IOPS, provisioned throughput, physical block size, storage pool and access mode. Requires project, zone, and disk name as input.
This record as markdown: /tools/com-googleapis-compute-mcp/get-disk-performance-config.md
What get_disk_performance_config does on Mcp
AI agents call get_disk_performance_config 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 disk name. |
zone | string | Yes | Required. The zone of the disk. |
project | string | Yes | Required. Project ID for this request. |
Parameters from the server's own tool schema.
Why get_disk_performance_config is rated Low
This is a straightforward read/query operation that retrieves configuration details about an existing Compute Engine disk. It has no side effects, does not modify infrastructure, and returns only informational data about disk properties. The required inputs (project, zone, disk name) are identifiers to scope the read operation.
From the tool's definition Tool name is 'get_disk_performance_config' and description states it 'Get[s] performance configuration' — purely retrieves disk metadata including type, size, IOPS, throughput, block size, storage pool, and access mode.
Attacks that exploit this kind of access
The rule that runs get_disk_performance_config 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 get_disk_performance_config, this is the rule to start with:
get_disk_performance_config 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 get_disk_performance_config call is checked against it from then on.
Questions about get_disk_performance_config
Get performance configuration of a Compute Engine disk, including its type, size, provisioned IOPS, provisioned throughput, physical block size, storage pool and access mode. Requires project, zone, and disk name as input. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
get_disk_performance_config 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.
Register the MCP server in PolicyLayer and add a rule for get_disk_performance_config: 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.
get_disk_performance_config 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 get_disk_performance_config 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 get_disk_performance_config. 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.
get_disk_performance_config 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