List every namespace present in stored memory.
AI agents call list_namespaces to retrieve information from State Trace without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about existing namespaces without creating, modifying, deleting, or executing anything. It is a pure data retrieval operation with minimal blast radius—an AI agent cannot cause harm by listing namespaces, though the information itself might reveal structural details of the memory system.
From the tool's definition Tool name 'list_namespaces' and description 'List every namespace present in stored memory' indicate a retrieval/query operation with no side effects. The verb 'list' is characteristic of Read category tools.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List every namespace present in stored memory. It is categorised as a Read tool in the State Trace MCP Server, which means it retrieves data without modifying state.
Register the State Trace MCP server in PolicyLayer and add a rule for list_namespaces: 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 State Trace. Nothing to install.
list_namespaces 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_namespaces 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_namespaces. 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_namespaces is provided by the State Trace MCP server (agent-pattern-labs/state-trace). 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 →