AI agents call list_memories to retrieve information from Memlord without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name and naming pattern strongly suggest this retrieves or queries a list of memories without modifying data. Although the description is empty and confidence is slightly reduced, the context of sibling tools performing read operations makes Read the most appropriate category.
From the tool's definition Tool name 'list_memories' indicates a listing/retrieval operation. No description provided, but the sibling tools include 'get_memory', 'retrieve_memory', 'search_by_tag', and 'recall_memory'—all Read operations—which contextually supports a Read…
Documented attack patterns abuse exactly the kind of access list_memories gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Memlord, and nothing reaches the server without passing your rules. This is the rule we recommend for list_memories:
{
"version": "1",
"default": "deny",
"tools": {
"list_memories": {}
}
}list_memories is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
list_memories. It is categorised as a Read tool in the Memlord MCP Server, which means it retrieves data without modifying state.
Register the Memlord MCP server in PolicyLayer and add a rule for list_memories: 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 Memlord. Nothing to install.
list_memories 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 list_memories 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 list_memories. 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.
list_memories is provided by the Memlord MCP server (myrikld/memlord). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Memlord, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 Memlord tools catalogued and risk-classified — across an index of 43,000+ MCP servers.