This tool lists all available namespaces with memory counts. Use to discover what namespaces exist.
AI agents call listNamespaces to retrieve information from MCP Memory without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries metadata about existing namespaces without side effects. It is informational only, falling squarely into the Read category. The low severity reflects minimal risk even if an agent enumerates all namespaces, as no data is deleted, modified, or executed.
From the tool's definition Tool description states 'lists all available namespaces with memory counts' and 'Use to discover what namespaces exist' — pure enumeration with no modification or execution.
Attacks that exploit this kind of access
This tool lists all available namespaces with memory counts. Use to discover what namespaces exist. It is categorised as a Read tool in the MCP Memory MCP Server, which means it retrieves data without modifying state.
Register the MCP Memory MCP server in PolicyLayer and add a rule for listNamespaces: 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 MCP Memory. Nothing to install.
listNamespaces 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 listNamespaces 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 listNamespaces. 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.
listNamespaces is provided by the MCP Memory MCP server (redaphid/mcp-memory). 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 →