Query the memory graph by canonical entity name. Use when you know the entity name or close-to-canonical form (e.g. \
AI agents call graph_query to retrieve information from Graph-Memory without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs read-only queries against the knowledge graph to retrieve information about entities. It has no capability to modify, delete, or execute operations—only to search and return data. The low severity reflects minimal blast radius; even if misused by an agent, it can only expose cached information already in the personal knowledge graph, not modify or delete it.
From the tool's definition Tool name 'graph_query' and description 'Query the memory graph by canonical entity name' indicate data retrieval with no modification or deletion.
Attacks that exploit this kind of access
Query the memory graph by canonical entity name. Use when you know the entity name or close-to-canonical form (e.g. \. It is categorised as a Read tool in the Graph-Memory MCP Server, which means it retrieves data without modifying state.
Register the Graph-Memory MCP server in PolicyLayer and add a rule for graph_query: 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.
graph_query 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 graph_query 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 graph_query. 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.
graph_query 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.
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 →