memory_create · Amazon ElastiCache Memcached MCP Server MCP

WHAT IT DOES

What memory_create does on Amazon ElastiCache Memcached MCP Server

AI agents use memory_create to create or update resources in Amazon ElastiCache Memcached MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Amazon ElastiCache Memcached MCP Server environment.

WHY IT NEEDS A POLICY

Why memory_create needs a policy

The tool creates data in ElastiCache Memcached (reversible write operation). While not destructive or dangerous by itself, misconfiguration or misuse could lead to cache pollution, memory exhaustion, or unintended state changes affecting downstream applications. Classified as Write rather than Read (retrieves data) or Execute (arbitrary code).

From the tool's definition Tool name 'memory_create' indicates creation of a memcached cache entry or memory object in ElastiCache. The empty description prevents direct confirmation, but the naming pattern (create operation) and context of an ElastiCache Memcached server strongly…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

memory_create Rate-limited

memory_create 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": {
    "memory_create": {
      "limits": [
        {
          "counter": "memory_create_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Amazon ElastiCache Memcached MCP Server, so you can run agents against it safely.

FAQ

Questions about memory_create

What does the memory_create tool do? +

memory_create. It is categorised as a Write tool in the Amazon ElastiCache Memcached MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on memory_create? +

Register the Amazon ElastiCache Memcached MCP Server MCP server in PolicyLayer and add a rule for memory_create: 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 Amazon ElastiCache Memcached MCP Server. Nothing to install.

What risk level is memory_create? +

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

Can I rate-limit memory_create? +

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

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

memory_create is provided by the Amazon ElastiCache Memcached MCP Server MCP server (awslabs.memcached-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.