memory_create_event · Awslabs Valkey MCP: Risk & Policy

WHAT IT DOES

What memory_create_event does on Awslabs Valkey

AI agents use memory_create_event to create or update resources in Awslabs Valkey — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Awslabs Valkey environment.

WHY IT NEEDS A POLICY

Why memory_create_event needs a policy

The tool name indicates creation of event data in a cache/memory database system. Write operations modify data reversibly and can be undone (unlike Destructive). Without a description, confidence is moderately reduced, but the 'create' verb and context of a MemoryDB tool make Write the most reasonable classification.

From the tool's definition Tool name 'memory_create_event' suggests creation of a new event entity in memory/cache storage; 'create' indicates a Write operation that modifies state in ElastiCache/MemoryDB.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

memory_create_event Rate-limited

memory_create_event 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_event": {
      "limits": [
        {
          "counter": "memory_create_event_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 Awslabs Valkey, so you can run agents against it safely.

FAQ

Questions about memory_create_event

What does the memory_create_event tool do? +

memory_create_event. It is categorised as a Write tool in the Awslabs Valkey 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_event? +

Register the Awslabs Valkey MCP server in PolicyLayer and add a rule for memory_create_event: 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 Awslabs Valkey. Nothing to install.

What risk level is memory_create_event? +

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

Can I rate-limit memory_create_event? +

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

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

memory_create_event is provided by the Awslabs Valkey MCP server (awslabs.valkey-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.