Index markdown documents from a directory into a named vault. Use to populate a vault with content from a specific path.
AI agents use vault_sync to create or update resources in ClawMem — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ClawMem environment.
The tool reads files from a directory and writes/indexes them into a named vault. This is a Write operation as it creates or modifies data (populating the vault index) in a reversible way. Misuse could index unintended content into the memory layer, affecting AI agent recall, hence medium severity.
From the tool's definition Index markdown documents from a directory into a named vault. Use to populate a vault with content from a specific path.
Documented attack patterns abuse exactly the kind of access vault_sync 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 vault_sync:
{
"version": "1",
"default": "deny",
"tools": {
"vault_sync": {
"limits": [
{
"counter": "vault_sync_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}vault_sync stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Index markdown documents from a directory into a named vault. Use to populate a vault with content from a specific path. It is categorised as a Write tool in the ClawMem MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ClawMem MCP server in PolicyLayer and add a rule for vault_sync: 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.
vault_sync is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the vault_sync 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 vault_sync. 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.
vault_sync 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.