memory_related

Find memories related to a given memory using knowledge graph traversal and/or semantic similarity. Combines two strategies: (1) graph edges created via graph_connect or memory_store\

Server Claude Session Continuity leesgit/claude-session-continuity-mcp
Category Read
Risk class Low
Parameters 00 required

What memory_related does on Claude Session Continuity

AI agents call memory_related to retrieve information from Claude Session Continuity without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why memory_related needs a policy

This tool performs a read-only retrieval operation that queries a knowledge graph to locate related memories. It traverses existing connections and performs semantic matching—both passive operations that retrieve data without modifying state, executing code, or triggering external effects.

From the tool's definition Tool description states it 'Find memories related to a given memory using knowledge graph traversal and/or semantic similarity.' The verb 'find' and the traversal/similarity operations are query/retrieval operations with no modification or side effects.

Questions about memory_related

What does the memory_related tool do? +

Find memories related to a given memory using knowledge graph traversal and/or semantic similarity. Combines two strategies: (1) graph edges created via graph_connect or memory_store\. It is categorised as a Read tool in the Claude Session Continuity MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on memory_related? +

Register the Claude Session Continuity MCP server in PolicyLayer and add a rule for memory_related: 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 Claude Session Continuity. Nothing to install.

What risk level is memory_related? +

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

Can I rate-limit memory_related? +

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

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

memory_related is provided by the Claude Session Continuity MCP server (leesgit/claude-session-continuity-mcp). 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.