set_instance_machine_type
Sets the machine type for a stopped Google Compute Engine instance to the specified machine type. Requires project, zone, instance name and machine type as input. Proceed only if there is no error in response and the status of the operation is DONE without any errors. To get details of the operat...
This record as markdown: /tools/com-googleapis-compute-mcp/set-instance-machine-type.md
What set_instance_machine_type does on Mcp
AI agents use set_instance_machine_type to create or update resources in Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp environment.
| 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. |
machineType | string | Yes | Required. The machine type of the instance. |
Parameters from the server's own tool schema.
Why set_instance_machine_type is rated Medium
This tool modifies instance configuration by changing the machine type, which is a reversible Write operation. While it affects infrastructure, the change can be undone by setting a different machine type.
From the tool's definition Tool description states it 'Sets the machine type for a stopped Google Compute Engine instance' - this is a modification operation that changes instance configuration.
Attacks that exploit this kind of access
The rule that runs set_instance_machine_type 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 set_instance_machine_type, this is the rule to start with:
set_instance_machine_type stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 set_instance_machine_type call is checked against it from then on.
Questions about set_instance_machine_type
Sets the machine type for a stopped Google Compute Engine instance to the specified machine type. Requires project, zone, instance name and machine type as input. Proceed only if there is no error in response and the status of the operation is DONE without any errors. To get details of the operation, use the get_zone_operation tool. It is categorised as a Write tool in the Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
set_instance_machine_type accepts 4 parameters: name, zone, project, machineType. Required: name, zone, project, machineType. 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 set_instance_machine_type: 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.
set_instance_machine_type is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_instance_machine_type 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 set_instance_machine_type. 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.
set_instance_machine_type 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