update_instance

Update a Memorystore for Valkey instance.

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

Medium RISK CLASS

Category Write

Parameters 31 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-googleapis-memorystore-mcp/update-instance.md

WHAT IT DOES

What update_instance does on Mcp

AI agents use update_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
`instance`	object	Yes	Required. The instance to update.
`requestId`	string	—	Optional. An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the re
`updateMask`	string	—	Optional. The list of fields to be updated on the instance. At least one field must be specified.

Parameters from the server's own tool schema.

RISK

Why update_instance is rated Medium

This tool modifies an existing Memorystore instance configuration reversibly. Updates are typically non-destructive changes (e.g., scaling, configuration adjustments) that can be rolled back or changed again, placing it in the Write category rather than Destructive. Severity is medium because misconfigured updates could impact service availability or performance, but the effects are generally reversible.

From the tool's definition Tool name is 'update_instance' and description states 'Update a Memorystore for Valkey instance.' The verb 'update' indicates modification of existing data/configuration.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

update_instance Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_instance": {
      "limits": [
        {
          "counter": "update_instance_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about update_instance

What does the update_instance tool do? +

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

What parameters does update_instance accept? +

update_instance accepts 3 parameters: instance, requestId, updateMask. Required: instance. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_instance? +

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

What risk level is update_instance? +

update_instance is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_instance? +

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

How do I block update_instance completely? +

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

What MCP server provides update_instance? +

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

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 14 tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →