List MCP-visible memory spaces that this server can route and recover.
AI agents call list_spaces to retrieve information from Evermemos without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward query operation that retrieves metadata about available memory spaces. It has no side effects, does not execute code, and does not modify or delete data. The blast radius of misuse is minimal—an attacker could only discover what memory spaces exist, which is low-sensitivity information in the context of a memory management system. It falls clearly into the Read category.
From the tool's definition The tool name 'list_spaces' and description 'List MCP-visible memory spaces' indicates a retrieval operation that enumerates available memory spaces without modifying, executing, or deleting anything.
Documented attack patterns abuse exactly the kind of access list_spaces gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Evermemos, and nothing reaches the server without passing your rules. This is the rule we recommend for list_spaces:
{
"version": "1",
"default": "deny",
"tools": {
"list_spaces": {}
}
}list_spaces 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.
List MCP-visible memory spaces that this server can route and recover. It is categorised as a Read tool in the Evermemos MCP Server, which means it retrieves data without modifying state.
Register the Evermemos MCP server in PolicyLayer and add a rule for list_spaces: 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 Evermemos. Nothing to install.
list_spaces 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_spaces 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_spaces. 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_spaces is provided by the Evermemos MCP server (tt-a1i/evermemos-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Evermemos, 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.
7 Evermemos tools catalogued and risk-classified — across an index of 43,000+ MCP servers.