Low Risk

memory_knowledge_graph

Query the knowledge graph for relationships and paths

How to control memory_knowledge_graph ↓

What memory_knowledge_graph does on Documcp

AI agents call memory_knowledge_graph to retrieve information from Documcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why memory_knowledge_graph needs a policy

The tool performs a query operation to retrieve structured information (relationships and paths) from an in-memory knowledge graph. This is a retrieval operation with no side effects, reversible modifications, code execution, or data destruction. Querying a knowledge graph is a fundamental Read operation.

From the tool's definition Tool description explicitly states 'Query the knowledge graph' — a read-only operation that retrieves relationships and paths without modifying data.

Documented attack patterns abuse exactly the kind of access memory_knowledge_graph gives an agent:

How to control memory_knowledge_graph

PolicyLayer is an MCP gateway — it sits between your AI agents and Documcp, and nothing reaches the server without passing your rules. This is the rule we recommend for memory_knowledge_graph:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "memory_knowledge_graph": {}
  }
}

memory_knowledge_graph is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Documcp — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about memory_knowledge_graph

What does the memory_knowledge_graph tool do? +

Query the knowledge graph for relationships and paths. It is categorised as a Read tool in the Documcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on memory_knowledge_graph? +

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

What risk level is memory_knowledge_graph? +

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

Can I rate-limit memory_knowledge_graph? +

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

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

memory_knowledge_graph is provided by the Docu MCP server (tosin2013/documcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Documcp tool call.

Start from Documcp, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

52 Documcp tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.