AI agents call remember_query_internal_memory to retrieve information from Remember without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves data from a memory system using natural language search without modifying, executing, or deleting anything. The session-scoping limits its blast radius to the caller's own data. The absence of mutation verbs (create, update, delete, execute) confirms it is a Read operation.
From the tool's definition Tool description states 'Query internal memories...using natural language (pure semantic search)' and is 'scoped to the current session'. The verb 'query' combined with 'semantic search' indicates read-only data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Query internal memories (ghost or agent) using natural language (pure semantic search). Automatically scoped to the current session. It is categorised as a Read tool in the Remember MCP Server, which means it retrieves data without modifying state.
Register the Remember MCP server in PolicyLayer and add a rule for remember_query_internal_memory: 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 Remember. Nothing to install.
remember_query_internal_memory 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 remember_query_internal_memory 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 remember_query_internal_memory. 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.
remember_query_internal_memory is provided by the Remember MCP server (@prmichaelsen/remember-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 →