get_backup_collection
Get detailed information about a Memorystore for Valkey backup collection.
This record as markdown: /tools/com-googleapis-memorystore-mcp/get-backup-collection.md
What get_backup_collection does on Mcp
AI agents call get_backup_collection 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 |
|---|---|---|---|
name | string | Yes | Required. Instance backupCollection resource name using the form: `projects/{project_id}/locations/{location_id}/backupCollections/{backup_collection_id}` where |
Parameters from the server's own tool schema.
Why get_backup_collection is rated Low
This tool retrieves and queries information about backup collections without creating, modifying, deleting, or executing any operations. It is purely informational, fitting the Read category for low-severity risk.
From the tool's definition Tool name 'get_backup_collection' and description 'Get detailed information about a Memorystore for Valkey backup collection' indicate a retrieval operation with no modification or execution.
Attacks that exploit this kind of access
The rule that runs get_backup_collection 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 get_backup_collection, this is the rule to start with:
get_backup_collection 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 get_backup_collection call is checked against it from then on.
Questions about get_backup_collection
Get detailed information about a Memorystore for Valkey backup collection. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
get_backup_collection accepts 1 parameter: name. 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 get_backup_collection: 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.
get_backup_collection 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 get_backup_collection 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 get_backup_collection. 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.
get_backup_collection 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