create_backup
Takes a backup on a Cloud SQL instance. Always populate the project and instance fields on the request. The location (region) and description of the backup may also be optionally provided, in which case the corresponding request fields should also be populated.
This record as markdown: /tools/com-googleapis-sqladmin-mcp/create-backup.md
What create_backup does on Mcp
AI agents use create_backup 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 |
|---|---|---|---|
project | string | Yes | Required. Project ID of the project that contains the instance. |
instance | string | Yes | Required. Cloud SQL instance ID. This does not include the project ID. |
location | string | — | Optional. Location of the backup run. |
description | string | — | Optional. The description of this backup run. |
Parameters from the server's own tool schema.
Why create_backup is rated Medium
Creating a backup is a write operation that creates a new cloud resource. While backups are protective in nature, the action itself creates persistent data/state that consumes resources and requires cleanup. It's reversible (backups can be deleted) and doesn't directly modify or destroy production data, so it ranks below Destructive/Execute.
From the tool's definition Tool name 'create_backup' and description 'Takes a backup on a Cloud SQL instance' indicate creating a new backup artifact without deleting or modifying existing data.
Attacks that exploit this kind of access
The rule that runs create_backup 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 create_backup, this is the rule to start with:
create_backup 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 create_backup call is checked against it from then on.
Questions about create_backup
Takes a backup on a Cloud SQL instance. Always populate the project and instance fields on the request. The location (region) and description of the backup may also be optionally provided, in which case the corresponding request fields should also be populated. 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.
create_backup accepts 4 parameters: project, instance, location, description. Required: 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 create_backup: 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.
create_backup 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 create_backup 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 create_backup. 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.
create_backup 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