list_backup_collections
List all Memorystore for Valkey backup collections.
This record as markdown: /tools/com-googleapis-memorystore-mcp/list-backup-collections.md
What list_backup_collections does on Mcp
AI agents call list_backup_collections to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
parent | string | Yes | Required. The resource name of the backupCollection location using the form: `projects/{project_id}/locations/{location_id}` where `location_id` refers to a Goo |
pageSize | integer | — | Optional. The maximum number of items to return. If not specified, a default value of 1000 will be used by the service. Regardless of the page_size value, the r |
pageToken | string | — | Optional. The `next_page_token` value returned from a previous `ListBackupCollections` request, if any. |
Parameters from the server's own tool schema.
Why list_backup_collections is rated Low
This tool retrieves and enumerates backup collections from Memorystore for Valkey. It performs a read-only operation with no side effects, data modification, or irreversible actions. The verb 'list' is characteristic of Read category operations.
From the tool's definition Tool name 'list_backup_collections' and description 'List all Memorystore for Valkey backup collections' indicate a query operation that retrieves information without modifying state.
Attacks that exploit this kind of access
The rule that runs list_backup_collections 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 list_backup_collections, this is the rule to start with:
list_backup_collections is read-only, so it stays allowed. 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 list_backup_collections call is checked against it from then on.
Questions about list_backup_collections
List all Memorystore for Valkey backup collections. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
list_backup_collections accepts 3 parameters: parent, pageSize, pageToken. Required: parent. 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 list_backup_collections: 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.
list_backup_collections is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_backup_collections 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 list_backup_collections. 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.
list_backup_collections 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