Returns a compact index of all accessible memories (id, summary, visibility, user, updatedAt). Call at session start and before memory_add to check for duplicates or memories to update. Max 100 results. You see: all org memories, user memories matching your user, and your own token memories.
AI agents call memory_list to retrieve information from Shellgate without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a pure data retrieval operation—querying and returning metadata about memories in an index format. It has no capacity to modify, delete, or execute operations. The visibility filtering (org, user, token-scoped) suggests appropriate access controls are in place.
From the tool's definition Tool name 'memory_list' and description 'Returns a compact index of all accessible memories (id, summary, visibility, user, updatedAt)' indicates a read-only query operation.
Documented attack patterns abuse exactly the kind of access memory_list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Shellgate, and nothing reaches the server without passing your rules. This is the rule we recommend for memory_list:
{
"version": "1",
"default": "deny",
"tools": {
"memory_list": {}
}
}memory_list 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.
Returns a compact index of all accessible memories (id, summary, visibility, user, updatedAt). Call at session start and before memory_add to check for duplicates or memories to update. Max 100 results. You see: all org memories, user memories matching your user, and your own token memories. It is categorised as a Read tool in the Shellgate MCP Server, which means it retrieves data without modifying state.
Register the Shellgate MCP server in PolicyLayer and add a rule for memory_list: 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 Shellgate. Nothing to install.
memory_list 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_list 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_list. 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_list is provided by the Shellgate MCP server (matthiastjong/shellgate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Shellgate, 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.
31 Shellgate tools catalogued and risk-classified — across an index of 43,000+ MCP servers.