List all structured memories with their schemas, record counts, and storage usage.
AI agents call list_memories to retrieve information from Structured-sh without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation that enumerates and describes existing memories without creating, modifying, deleting, or executing anything. The information returned (schemas, counts, usage) is metadata about stored state. No side effects occur from calling this tool. Severity is low because listing data has minimal blast radius even if misused by an agent.
From the tool's definition Tool name 'list_memories' and description 'List all structured memories with their schemas, record counts, and storage usage' indicate a retrieval/query operation with no modification or deletion of data.
Attacks that exploit this kind of access
List all structured memories with their schemas, record counts, and storage usage. It is categorised as a Read tool in the Structured-sh MCP Server, which means it retrieves data without modifying state.
Register the Structured-sh 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 Structured-sh. 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 Structured-sh MCP server (structured-sh/structured). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →