memory_get
AI agents call memory_get 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.
The 'get' verb in 'memory_get' strongly suggests a retrieval operation with no side effects. On a Valkey/MemoryDB server, GET operations are foundational read commands that fetch values from the cache. While the description is empty (reducing confidence slightly), the naming convention and context of an in-memory data store establish this as a Read operation.
From the tool's definition Tool name 'memory_get' indicates a retrieval operation from an in-memory data store (Valkey/Redis). The function name follows the standard pattern for read-only GET operations that query cached data without modification.
Attacks that exploit this kind of access
memory_get. It is categorised as a Read tool in the Awslabs Valkey MCP Server, which means it retrieves data without modifying state.
Register the Awslabs Valkey MCP server in PolicyLayer and add a rule for memory_get: 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.
memory_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the memory_get 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.
Set action: deny in the PolicyLayer policy for memory_get. 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.
memory_get 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.