memory_get_record

memory_get_record

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

What memory_get_record does on Awslabs Valkey

AI agents call memory_get_record 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_record needs a policy

Despite the empty description, the naming convention 'get_record' strongly suggests a retrieval operation that queries data without side effects. In the context of a Valkey/MemoryDB server (in-memory data store), 'get' operations retrieve cached values. This is a Read operation with low severity because it does not modify, execute code, delete data, or involve financial transactions.

From the tool's definition Tool name 'memory_get_record' indicates retrieval of a record from memory/cache storage (MemoryDB/Valkey). The 'get' operation is characteristic of read-only data access patterns.

Questions about memory_get_record

What does the memory_get_record tool do? +

memory_get_record. 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_record? +

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

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

Can I rate-limit memory_get_record? +

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

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

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