Open and display information about a memory file. Returns metadata including: - Frame count - Index sizes (lexical, vector, temporal) - Creation date - Last modified date Args: file: Path to the .mv2 memory file Returns: JSON with file metadata and statistics
AI agents call memvid_open 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 purely retrieves and displays metadata about a memory file. It has no side effects, does not modify any data, and only returns informational statistics about the file.
From the tool's definition Open and display information about a memory file. Returns metadata including: Frame count, Index sizes, Creation date, Last modified date
Attacks that exploit this kind of access
Open and display information about a memory file. Returns metadata including: - Frame count - Index sizes (lexical, vector, temporal) - Creation date - Last modified date Args: file: Path to the .mv2 memory file Returns: JSON with file metadata and statistics. 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_open: 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_open 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_open 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_open. 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_open 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.
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 →