Read the entire knowledge graph
AI agents call read_graph to retrieve information from Loc Knowledge Graph Memory Server 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 the knowledge graph without creating, modifying, or deleting any data. It has no side effects beyond information access. The knowledge graph contains user information, but reading it poses minimal risk compared to write or destructive operations. Severity is low because access is already within the Claude-user context where the data was stored.
From the tool's definition Tool description explicitly states 'Read the entire knowledge graph' with the verb 'read' indicating data retrieval with no modification.
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 Loc Knowledge Graph Memory Server MCP Server, which means it retrieves data without modifying state.
Register the Loc Knowledge Graph Memory Server 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 Loc Knowledge Graph Memory Server. 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 Loc Knowledge Graph Memory Server MCP server (myangsun/loc-memory-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →