export_backup
Export a Memorystore for Valkey backup.
This record as markdown: /tools/com-googleapis-memorystore-mcp/export-backup.md
What export_backup does on Mcp
AI agents use export_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 |
|---|---|---|---|
name | string | Yes | Required. Instance backup resource name using the form: `projects/{project_id}/locations/{location_id}/backupCollections/{backup_collection_id}/backups/{backup_ |
gcsBucket | string | — | Google Cloud Storage bucket, like "my-bucket". |
Parameters from the server's own tool schema.
Why export_backup is rated Medium
This tool creates or generates a new export artifact from an existing backup, which is a reversible write operation. It does not delete, execute arbitrary code, or modify the backup itself. The severity is medium because exporting sensitive data could expose credentials or sensitive information if not properly secured, but the operation is reversible and does not directly modify or destroy data in the system.
From the tool's definition Tool name 'export_backup' combined with description 'Export a Memorystore for Valkey backup' indicates data extraction/output generation. Exporting creates a new artifact (exported backup file) derived from existing data.
Attacks that exploit this kind of access
The rule that runs export_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 export_backup, this is the rule to start with:
export_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 export_backup call is checked against it from then on.
Questions about export_backup
Export a Memorystore for Valkey backup. 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.
export_backup accepts 2 parameters: name, gcsBucket. 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 export_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.
export_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 export_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 export_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.
export_backup 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