list_instances

List all Memorystore for Valkey instances.

SERVERMcp SOURCEhttps://memorystore.googleapis.com/mcp

Low RISK CLASS

Category Read

Parameters 51 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-googleapis-memorystore-mcp/list-instances.md

WHAT IT DOES

What list_instances does on Mcp

AI agents call list_instances 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
`filter`	string	—	Optional. Expression for filtering results.
`parent`	string	Yes	Required. The parent to list instances from. Format: projects/{project}/locations/{location}
`orderBy`	string	—	Optional. Sort results by a defined order. Supported values: "name", "create_time".
`pageSize`	integer	—	Optional. Requested page size. Server may return fewer items than requested. If unspecified, server will pick an appropriate default.
`pageToken`	string	—	Optional. A token identifying a page of results the server should return.

Parameters from the server's own tool schema.

RISK

Why list_instances is rated Low

This tool retrieves and enumerates existing Memorystore for Valkey instances without modifying, executing, deleting, or committing any operations. The action is informational only, making it a Read category risk with low severity.

From the tool's definition Tool name 'list_instances' and description 'List all Memorystore for Valkey instances' indicate a read-only retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_instances 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_instances, this is the rule to start with:

list_instances Allowed

list_instances is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_instances": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every list_instances call is checked against it from then on.

FAQ

Questions about list_instances

What does the list_instances tool do? +

List all Memorystore for Valkey instances. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.

What parameters does list_instances accept? +

list_instances accepts 5 parameters: filter, parent, orderBy, pageSize, pageToken. Required: parent. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_instances? +

Register the MCP server in PolicyLayer and add a rule for list_instances: 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.

What risk level is list_instances? +

list_instances is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_instances? +

Yes. Add a rate_limit block to the list_instances 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.

How do I block list_instances completely? +

Set action: deny in the PolicyLayer policy for list_instances. 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.

What MCP server provides list_instances? +

list_instances 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.

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 14 tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →