Entity lookup - find information about an entity. Searches for entity mentions and related information. Args: file: Path to the .mv2 memory file query: Entity name or search query Returns: Entity information and mentions
AI agents call memvid_who to retrieve information from Memvid without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries data about entities within a memory file without creating, modifying, deleting, or executing arbitrary operations. It is a straightforward search/lookup operation with read-only semantics, making it a Read category tool with low severity and high confidence.
From the tool's definition Tool description states 'Entity lookup - find information about an entity' and 'Searches for entity mentions and related information.' The args are a file path and query string, with no parameters for modification or deletion.
Attacks that exploit this kind of access
Entity lookup - find information about an entity. Searches for entity mentions and related information. Args: file: Path to the .mv2 memory file query: Entity name or search query Returns: Entity information and mentions. It is categorised as a Read tool in the Memvid MCP Server, which means it retrieves data without modifying state.
Register the Memvid MCP server in PolicyLayer and add a rule for memvid_who: 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 Memvid. Nothing to install.
memvid_who 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 memvid_who 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 memvid_who. 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.
memvid_who is provided by the Memvid MCP server (tapiocapioca/memvid-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
memvid_who is one line of Memvid's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →