Traverse relationships from a known entity in the knowledge graph. Use when you want to explore what an entity is connected to — colleagues, projects, organizations. Use graph_search first if you need to find the entity_id.
AI agents call graph_traverse to retrieve information from Memsolus MCP Server 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 navigation through a knowledge graph to retrieve relationship information. It queries and explores data without creating, modifying, deleting, or executing any operations. The most severe risk is information disclosure from existing graph data, which is the lowest category. Low severity reflects that graph traversal cannot cause side effects or data loss.
From the tool's definition Tool description states 'Traverse relationships from a known entity' and 'explore what an entity is connected to' — these are query/retrieval operations. The verb 'traverse' indicates navigation of existing data structures without modification.
Attacks that exploit this kind of access
Traverse relationships from a known entity in the knowledge graph. Use when you want to explore what an entity is connected to — colleagues, projects, organizations. Use graph_search first if you need to find the entity_id. It is categorised as a Read tool in the Memsolus MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Memsolus MCP Server MCP server in PolicyLayer and add a rule for graph_traverse: 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 Memsolus MCP Server. Nothing to install.
graph_traverse 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_traverse 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_traverse. 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_traverse is provided by the Memsolus MCP Server MCP server (memsolus/mcp). 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 →