graph_ingest · Graph-Memory MCP: Risk & Policy

WHAT IT DOES

What graph_ingest does on Graph-Memory

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

WHY IT NEEDS A POLICY

Why graph_ingest needs a policy

This tool ingests/queues a document for processing and extraction into the knowledge graph, which is a write operation — it creates new nodes/relationships in the graph from document content. It is reversible in principle (the added data could be deleted), so Write is appropriate rather than Destructive.

From the tool's definition Queue a document for asynchronous extraction into the memory graph

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

graph_ingest Rate-limited

graph_ingest 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": {
    "graph_ingest": {
      "limits": [
        {
          "counter": "graph_ingest_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 Graph-Memory, so you can run agents against it safely.

FAQ

Questions about graph_ingest

What does the graph_ingest tool do? +

Queue a document for asynchronous extraction into the memory graph (mode=. It is categorised as a Write tool in the Graph-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 graph_ingest? +

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

What risk level is graph_ingest? +

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

Can I rate-limit graph_ingest? +

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

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

graph_ingest is provided by the Graph-Memory MCP server (stevepridemore/graph-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.