Show all configured vault names and their SQLite paths. Returns empty if running in single-vault mode (default).
AI agents call list_vaults to retrieve information from ClawMem without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and displays metadata about configured vault storage locations. It performs no modifications, executions, deletions, or financial operations. The blast radius of misuse is minimal—an agent could learn vault names and paths but cannot modify or access vault contents through this tool alone. This is a straightforward read operation with low security risk.
From the tool's definition Tool name 'list_vaults' and description 'Show all configured vault names and their SQLite paths' indicate a retrieval operation with no side effects. The verb 'Show' and the fact it 'Returns' information confirms this is a query/inspection function.
Documented attack patterns abuse exactly the kind of access list_vaults gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ClawMem, and nothing reaches the server without passing your rules. This is the rule we recommend for list_vaults:
{
"version": "1",
"default": "deny",
"tools": {
"list_vaults": {}
}
} list_vaults 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.
Show all configured vault names and their SQLite paths. Returns empty if running in single-vault mode (default). It is categorised as a Read tool in the ClawMem MCP Server, which means it retrieves data without modifying state.
Register the ClawMem MCP server in PolicyLayer and add a rule for list_vaults: 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 ClawMem. Nothing to install.
list_vaults 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_vaults 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_vaults. 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_vaults is provided by the ClawMem MCP server (yoloshii/clawmem). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 30 ClawMem tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
30 ClawMem tools catalogued and risk-classified — across an index of 42,500+ MCP servers.