Read the entire knowledge graph
AI agents call read_graph to retrieve information from MCP Memory Server - HTTP Streaming without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries data (the entire knowledge graph) without side effects. It performs no creation, modification, deletion, or execution of external operations. The severity is low because reading a knowledge graph poses minimal risk even if misused by an AI agent—it only exposes stored information without altering state or triggering external actions.
From the tool's definition Tool name is 'read_graph' and description states 'Read the entire knowledge graph' — explicitly a read operation with no modification or deletion of data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Read the entire knowledge graph. It is categorised as a Read tool in the MCP Memory Server - HTTP Streaming MCP Server, which means it retrieves data without modifying state.
Register the MCP Memory Server - HTTP Streaming MCP server in PolicyLayer and add a rule for read_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 MCP Memory Server - HTTP Streaming. Nothing to install.
read_graph is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the read_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.
Set action: deny in the PolicyLayer policy for read_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.
read_graph is provided by the MCP Memory Server - HTTP Streaming MCP server (songlairui/mcp-memory-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
read_graph is one line of MCP Memory Server - HTTP Streaming's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →