Get relevant context for a query based on conversation history and stored memories
AI agents call context_inject to retrieve information from MCP Memory Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves data (context, conversation history, stored memories) without creating, modifying, or deleting any information. It performs semantic lookup based on input but does not alter state. The blast radius of misuse is minimal—an AI agent could retrieve irrelevant or sensitive stored context, but cannot cause data loss, execute commands, or trigger external operations.
From the tool's definition Tool description states 'Get relevant context' — a retrieval operation with no modification or deletion. The verb 'Get' and the purpose of accessing 'conversation history and stored memories' indicate a read-only query operation.
Attacks that exploit this kind of access
Get relevant context for a query based on conversation history and stored memories. It is categorised as a Read tool in the MCP Memory Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Memory Server MCP server in PolicyLayer and add a rule for context_inject: 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 MCP Memory Server. Nothing to install.
context_inject 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 context_inject 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 context_inject. 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.
context_inject is provided by the MCP Memory Server MCP server (plumycat/mcp-memory-server). 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 →