memory_sync_from_vault · Agent Memory MCP: Risk & Policy

WHAT IT DOES

What memory_sync_from_vault does on Agent Memory

AI agents use memory_sync_from_vault to create or update resources in Agent Memory — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Agent Memory environment.

WHY IT NEEDS A POLICY

Why memory_sync_from_vault needs a policy

This tool imports/ingests Markdown files from an external Obsidian vault into the SQLite database. It creates new records (Write), but does not delete, overwrite, or execute arbitrary code. The description specifies 'new' files, suggesting it only adds rather than destructively overwrites. Misuse could flood the memory store with unwanted content, hence medium severity.

From the tool's definition Import new Markdown files from Obsidian vault into the database

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

memory_sync_from_vault Rate-limited

memory_sync_from_vault 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "memory_sync_from_vault": {
      "limits": [
        {
          "counter": "memory_sync_from_vault_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Agent Memory, so you can run agents against it safely.

FAQ

Questions about memory_sync_from_vault

What does the memory_sync_from_vault tool do? +

Import new Markdown files from Obsidian vault into the database. It is categorised as a Write tool in the Agent Memory MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on memory_sync_from_vault? +

Register the Agent Memory MCP server in PolicyLayer and add a rule for memory_sync_from_vault: 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 Agent Memory. Nothing to install.

What risk level is memory_sync_from_vault? +

memory_sync_from_vault is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit memory_sync_from_vault? +

Yes. Add a rate_limit block to the memory_sync_from_vault 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.

How do I block memory_sync_from_vault completely? +

Set action: deny in the PolicyLayer policy for memory_sync_from_vault. 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.

What MCP server provides memory_sync_from_vault? +

memory_sync_from_vault is provided by the Agent Memory MCP server (khaled1174/agent-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.