write_project_memory · MEMGRAPH- MCP: Risk & Policy

WHAT IT DOES

What write_project_memory does on MEMGRAPH-MCP

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

WHY IT NEEDS A POLICY

Why write_project_memory needs a policy

This tool creates or modifies memory entries in a backing store (SQLite-backed per server description). It has reversible effects—entries can be updated or managed—making it a Write operation.

From the tool's definition Tool description explicitly states 'Write a durable memory entry with provenance to the backing store.' The verb 'write' and terminology 'durable memory entry' indicate data creation/modification in a persistent store.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

write_project_memory Rate-limited

write_project_memory 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": {
    "write_project_memory": {
      "limits": [
        {
          "counter": "write_project_memory_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 MEMGRAPH-MCP, so you can run agents against it safely.

FAQ

Questions about write_project_memory

What does the write_project_memory tool do? +

Write a durable memory entry with provenance to the backing store. It is categorised as a Write tool in the MEMGRAPH-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on write_project_memory? +

Register the MEMGRAPH- MCP server in PolicyLayer and add a rule for write_project_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 MEMGRAPH-MCP. Nothing to install.

What risk level is write_project_memory? +

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

Can I rate-limit write_project_memory? +

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

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

write_project_memory is provided by the MEMGRAPH- MCP server (mikeb317/memgraph-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.