This record as markdown: /tools/frontmcp/list-memories.md
What list_memories does on Frontmcp
AI agents call list_memories to retrieve information from Frontmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_memories is rated Low
This tool queries or retrieves data (keys stored in memory within a scope) without modifying, creating, deleting, or executing anything. It is a straightforward read operation. Severity is low because listing keys poses minimal risk—it exposes only metadata about what is remembered, not sensitive values themselves, and causes no state changes.
From the tool's definition Tool name 'list_memories' and description 'List all remembered keys in a scope' indicate a retrieval operation with no side effects. The verb 'list' is characteristic of read-only operations.
Attacks that exploit this kind of access
The rule that runs list_memories safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Frontmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_memories, this is the rule to start with:
list_memories is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Frontmcp, apply this rule, and every list_memories call is checked against it from then on.
Questions about list_memories
List all remembered keys in a scope. It is categorised as a Read tool in the Frontmcp MCP Server, which means it retrieves data without modifying state.
Register the Front 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 Frontmcp. 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 Front MCP server (agentfront/frontmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Front, and thousands of servers like it.
This server
Across the catalogue