sync_central_memory

Sync the active project knowledge graph into the central memory database (~/memory/memory.db by default) so all projects share one searchable map

SERVERProject Guardian MCP SOURCE1999azzar/project-guardian-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/1999azzar-project-guardian-mcp-server/sync-central-memory.md

WHAT IT DOES

What sync_central_memory does on Project Guardian MCP

AI agents call sync_central_memory to retrieve information from Project Guardian MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why sync_central_memory is rated Low

Even though sync_central_memory only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sync_central_memory safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Project Guardian MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sync_central_memory, this is the rule to start with:

sync_central_memory Allowed

sync_central_memory is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sync_central_memory": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Project Guardian MCP, apply this rule, and every sync_central_memory call is checked against it from then on.

FAQ

Questions about sync_central_memory

What does the sync_central_memory tool do? +

Sync the active project knowledge graph into the central memory database (~/memory/memory.db by default) so all projects share one searchable map. It is categorised as a Read tool in the Project Guardian MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on sync_central_memory? +

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

What risk level is sync_central_memory? +

sync_central_memory is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit sync_central_memory? +

Yes. Add a rate_limit block to the sync_central_memory 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 sync_central_memory completely? +

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

sync_central_memory is provided by the Project Guardian MCP server (1999azzar/project-guardian-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Project Guardian, and thousands of servers like it.

This server

All 38 Project Guardian tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →