Return saved memory relevant to a query for future AI coding sessions.
AI agents call get_relevant_context to retrieve information from OpenMemBrain without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves previously saved memory content based on a user's input query. It has no side effects: it does not create, modify, delete, or execute anything. While the broader OpenMemBrain system autonomously absorbs project knowledge (which could include sensitive information), this specific tool is read-only.
From the tool's definition Tool name is 'get_relevant_context' and description states it 'Return[s] saved memory relevant to a query' — purely a retrieval operation with no modification, deletion, or execution of code.
Attacks that exploit this kind of access
Return saved memory relevant to a query for future AI coding sessions. It is categorised as a Read tool in the OpenMemBrain MCP Server, which means it retrieves data without modifying state.
Register the OpenMemBrain MCP server in PolicyLayer and add a rule for get_relevant_context: 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 OpenMemBrain. Nothing to install.
get_relevant_context 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_context 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_context. 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_context is provided by the OpenMemBrain MCP server (mohamadalhusseinie/openmembrain). 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 →