Incrementally sync memories to an Obsidian vault. Only writes files for memories created or updated since the last sync. Each memory becomes a .md file with frontmatter, organized by namespace and tier.
AI agents use memory_obsidian_sync to create or update resources in Exocortex — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Exocortex environment.
This tool writes markdown files to an Obsidian vault on disk, creating or updating files based on memory state. It is a Write operation (creating/modifying .md files), not Destructive since it only adds/updates files that have changed since the last sync.
From the tool's definition Incrementally sync memories to an Obsidian vault. Only writes files for memories created or updated since the last sync. Each memory becomes a .md file with frontmatter, organized by namespace and tier.
Attacks that exploit this kind of access
Incrementally sync memories to an Obsidian vault. Only writes files for memories created or updated since the last sync. Each memory becomes a .md file with frontmatter, organized by namespace and tier. It is categorised as a Write tool in the Exocortex MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Exocortex MCP server in PolicyLayer and add a rule for memory_obsidian_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 Exocortex. Nothing to install.
memory_obsidian_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 memory_obsidian_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 memory_obsidian_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.
memory_obsidian_sync is provided by the Exocortex MCP server (shawnhack/exocortex). 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 →