gcp_compute_create_instance
Create a new Compute Engine VM instance
This record as markdown: /tools/ahmedselimmansor-ctrl-gcp-mcp-server/gcp-compute-create-instance.md
What gcp_compute_create_instance does on GCP MCP Server
AI agents use gcp_compute_create_instance to create or update resources in GCP MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GCP MCP Server environment.
Why gcp_compute_create_instance is rated Medium
This tool creates a new VM instance, which is a reversible write operation that provisions cloud infrastructure and incurs costs. While it has financial implications (resource consumption), the primary action is infrastructure creation rather than financial transaction. It is Write rather than Execute because it does not run arbitrary code or trigger uncontrolled external operations—it provisions a specific resource.
From the tool's definition Tool name 'gcp_compute_create_instance' and description 'Create a new Compute Engine VM instance' indicate creation of cloud infrastructure resources.
Attacks that exploit this kind of access
The rule that runs gcp_compute_create_instance safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GCP MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gcp_compute_create_instance, this is the rule to start with:
gcp_compute_create_instance 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 GCP MCP Server, apply this rule, and every gcp_compute_create_instance call is checked against it from then on.
Questions about gcp_compute_create_instance
Create a new Compute Engine VM instance. It is categorised as a Write tool in the GCP MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GCP MCP Server MCP server in PolicyLayer and add a rule for gcp_compute_create_instance: 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 GCP MCP Server. Nothing to install.
gcp_compute_create_instance 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 gcp_compute_create_instance 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 gcp_compute_create_instance. 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.
gcp_compute_create_instance is provided by the GCP MCP Server MCP server (ahmedselimmansor-ctrl/gcp_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GCP MCP Server, and thousands of servers like it.
This server
Across the catalogue