get_relevant_reflections
Reflections relevant to a session: matches by sourceSessionId, plus evidence overlap with the supplied session entity names. Use at session start to surface applicable past lessons.
This record as markdown: /tools/danielsimonjr-memory-mcp/get-relevant-reflections.md
What get_relevant_reflections does on Enhanced Knowledge Graph Memory Server
AI agents call get_relevant_reflections to retrieve information from Enhanced Knowledge Graph Memory Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_relevant_reflections is rated Low
This tool performs a query operation that retrieves and matches historical reflection data without side effects. It reads from the knowledge graph to find relevant past information for the current session. No data is created, modified, deleted, or executed—only retrieved based on filtering criteria. This is a pure Read operation with minimal security risk.
From the tool's definition Tool retrieves reflections based on session ID and entity name matching; described as 'surface applicable past lessons' with no modification or deletion of data.
Attacks that exploit this kind of access
The rule that runs get_relevant_reflections safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Enhanced Knowledge Graph Memory Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_relevant_reflections, this is the rule to start with:
get_relevant_reflections is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Enhanced Knowledge Graph Memory Server, apply this rule, and every get_relevant_reflections call is checked against it from then on.
Questions about get_relevant_reflections
Reflections relevant to a session: matches by sourceSessionId, plus evidence overlap with the supplied session entity names. Use at session start to surface applicable past lessons. It is categorised as a Read tool in the Enhanced Knowledge Graph Memory Server MCP Server, which means it retrieves data without modifying state.
Register the Enhanced Knowledge Graph Memory Server MCP server in PolicyLayer and add a rule for get_relevant_reflections: 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 Enhanced Knowledge Graph Memory Server. Nothing to install.
get_relevant_reflections 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 get_relevant_reflections 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 get_relevant_reflections. 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.
get_relevant_reflections is provided by the Enhanced Knowledge Graph Memory Server MCP server (danielsimonjr/memory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Enhanced Knowledge Graph Memory Server, and thousands of servers like it.
Across the catalogue