backup_instance
Back up a Memorystore for Valkey instance.
This record as markdown: /tools/com-googleapis-memorystore-mcp/backup-instance.md
What backup_instance does on Mcp
AI agents use backup_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 |
|---|---|---|---|
ttl | string | — | Optional. TTL for the backup to expire. Value range is 1 day to 100 years. If not specified, the default value is 100 years. |
name | string | Yes | Required. Instance resource name using the form: `projects/{project_id}/locations/{location_id}/instances/{instance_id}` where `location_id` refers to a Google |
backupId | string | — | Optional. The id of the backup to be created. If not specified, the default value ([YYYYMMDDHHMMSS]_[Shortened Instance UID] is used. |
Parameters from the server's own tool schema.
Why backup_instance is rated Medium
Creating a backup is a Write operation — it produces a new backup artifact without destroying or modifying the source instance. It is reversible in the sense that the backup can be deleted afterward. Severity is medium because misuse could consume significant storage resources or trigger unintended backup billing, but it does not destroy data or move money.
From the tool's definition Back up a Memorystore for Valkey instance
Attacks that exploit this kind of access
The rule that runs backup_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 backup_instance, this is the rule to start with:
backup_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 backup_instance call is checked against it from then on.
Questions about backup_instance
Back up a Memorystore for Valkey instance. 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.
backup_instance accepts 3 parameters: ttl, name, backupId. Required: name. 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 backup_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.
backup_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 backup_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 backup_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.
backup_instance is provided by the MCP server (https://memorystore.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