mcp-memory/agent-rules/mcp_memory_integrity.md

MCP Memory Integrity Rule

CRITICAL RULE: Under NO CIRCUMSTANCES should any agent or subagent directly manipulate, edit, or write raw JSON/data to the MCP Memory Graph files (e.g., knowledge_graph_master.json, .db files, or any files inside ~/.gemini/mcp_memory/).

All interactions, additions, creations, and updates to the knowledge graph or task tracker MUST go through the officially exposed MCP tools (such as add_task, set_acceptance_criteria, verify_acceptance_criteria, log_code_change, create_entities, etc.).

Bypassing the MCP API by using file-editing tools (like replace_file_content or write_to_file) on the database files corrupts the state, bypasses indexing, and destroys the Redb Write-Ahead Log (WAL). If an agent attempts to do this, immediately stop them and route the request correctly through the provided MCP API tools.