clone_instance
Create a Cloud SQL instance as a clone of a source instance. * This tool returns a long-running operation. Use the get_operation tool to poll its status until the operation completes. * The clone operation can take several minutes. Use a command line tool to pause for 30 seconds before rechecking...
This record as markdown: /tools/com-googleapis-sqladmin-mcp/clone-instance.md
What clone_instance does on Mcp
AI agents use clone_instance 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 |
|---|---|---|---|
body | object | Yes | |
project | string | Yes | Required. Project ID of the source Cloud SQL instance. |
instance | string | Yes | Required. The ID of the Cloud SQL instance to be cloned (source). This does not include the project ID. |
location | string | — | Optional. Region of the Cloud SQL instance. |
Parameters from the server's own tool schema.
Why clone_instance is rated Medium
An AI agent can call clone_instance faster than any human can review: one bad instruction and it creates or modifies resources in Mcp by the hundred, each call as confident as the last.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs clone_instance 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 clone_instance, this is the rule to start with:
clone_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 Mcp, apply this rule, and every clone_instance call is checked against it from then on.
Questions about clone_instance
Create a Cloud SQL instance as a clone of a source instance. * This tool returns a long-running operation. Use the get_operation tool to poll its status until the operation completes. * The clone operation can take several minutes. Use a command line tool to pause for 30 seconds before rechecking the status. 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.
clone_instance accepts 4 parameters: body, project, instance, location. Required: body, project, instance. 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 clone_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 Mcp. Nothing to install.
clone_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 clone_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 clone_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.
clone_instance is provided by the MCP server (https://sqladmin.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