New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

create_instance

Create a Memorystore for Valkey instance.

SERVERMcp SOURCEhttps://memorystore.googleapis.com/mcp
Medium RISK CLASS
Category Write
Parameters 43 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/create-instance.md

What create_instance does on Mcp

AI agents use create_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.

ParameterTypeRequiredDescription
parent string Yes Required. The parent resource where this instance will be created. Format: projects/{project}/locations/{location}
instance object Yes Required. The instance to create.
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
instanceId string Yes Required. The ID to use for the instance, which will become the final component of the instance's resource name. This value is subject to the following restrict

Parameters from the server's own tool schema.

Why create_instance is rated Medium

This tool creates a new Memorystore for Valkey instance, which is a write operation that modifies cloud infrastructure state. While reversible (unlike destructive operations), it has high severity because creating instances can incur ongoing costs and consume quota/resources.

From the tool's definition Tool name 'create_instance' and description 'Create a Memorystore for Valkey instance' indicate data structure creation that is reversible (via delete_instance).

Questions about create_instance

What does the create_instance tool do? +

Create 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 create_instance accept? +

create_instance accepts 4 parameters: parent, instance, requestId, instanceId. Required: parent, instance, instanceId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on create_instance? +

Register the MCP server in PolicyLayer and add a rule for create_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 create_instance? +

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

Can I rate-limit create_instance? +

Yes. Add a rate_limit block to the create_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 create_instance completely? +

Set action: deny in the PolicyLayer policy for create_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 create_instance? +

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

More on , and thousands of servers like it.

This server

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of 's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.