search_memories
AI agents call search_memories to retrieve information from Vector Memory MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool searches and retrieves memory records semantically without modifying, deleting, or executing code. It follows the Read category pattern (search, query, fetch operations). Severity is low because retrieval operations on a memory database have minimal blast radius—an agent cannot cause irreversible damage or financial harm through search alone.
From the tool's definition Tool name 'search_memories' combined with server's stated purpose of 'semantic search and organization' indicates a query operation. The tool description is empty, but the function name and context clearly indicate data retrieval without side effects.
Attacks that exploit this kind of access
search_memories. It is categorised as a Read tool in the Vector Memory MCP MCP Server, which means it retrieves data without modifying state.
Register the Vector Memory MCP server in PolicyLayer and add a rule for search_memories: 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 Vector Memory MCP. Nothing to install.
search_memories 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 search_memories 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 search_memories. 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.
search_memories is provided by the Vector Memory MCP server (xsaven/vector-memory-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 →