memory_get_event

memory_get_event

Server Awslabs Valkey awslabs.valkey-mcp-server
Category Read
Risk class Low
Parameters 00 required

What memory_get_event does on Awslabs Valkey

AI agents call memory_get_event to retrieve information from Awslabs Valkey without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why memory_get_event needs a policy

Valkey (Redis fork) GET operations retrieve data without modification or side effects. Even though the description is empty, the tool name strongly suggests a read operation ('get') on cached event data. In a cache context, this poses minimal security risk—it retrieves existing data without persistence changes, user impact, or external effects. Low severity reflects limited blast radius if misused.

From the tool's definition Tool name 'memory_get_event' in a Valkey/Redis cache context indicates retrieval of events from memory storage. No description provided, but the 'get' operation pattern is characteristic of read-only data retrieval.

Questions about memory_get_event

What does the memory_get_event tool do? +

memory_get_event. It is categorised as a Read tool in the Awslabs Valkey MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on memory_get_event? +

Register the Awslabs Valkey MCP server in PolicyLayer and add a rule for memory_get_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_get_event? +

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

Can I rate-limit memory_get_event? +

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

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

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

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.