graph_entities

Browse or search the entity catalog. Use to check if an entity exists before creating one with graph_relate, or to list entities of a given type. For relationship-aware lookups (entity + its neighbors) use graph_query instead. Returns up to

Server Graph-Memory stevepridemore/graph-memory
Category Read
Risk class Low
Parameters 00 required

What graph_entities does on Graph-Memory

AI agents call graph_entities 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.

Why graph_entities needs a policy

graph_entities retrieves and searches existing entities from the knowledge graph without modifying, deleting, or executing operations. It is a pure data retrieval tool with minimal blast radius if misused by an agent—it can only expose existing stored information.

From the tool's definition Tool description: 'Browse or search the entity catalog' and 'list entities of a given type' — these are query/lookup operations with no side effects.

Questions about graph_entities

What does the graph_entities tool do? +

Browse or search the entity catalog. Use to check if an entity exists before creating one with graph_relate, or to list entities of a given type. For relationship-aware lookups (entity + its neighbors) use graph_query instead. Returns up to. It is categorised as a Read tool in the Graph-Memory MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on graph_entities? +

Register the Graph-Memory MCP server in PolicyLayer and add a rule for graph_entities: 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_entities? +

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

Can I rate-limit graph_entities? +

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

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

graph_entities 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.