Temporal search - find when something was mentioned. Searches for content and returns results with temporal context. Args: file: Path to the .mv2 memory file query: Time-related search query limit: Maximum results (default: 10) Returns: Results with timestamps showing when topics were mentioned
AI agents call memvid_when 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 is a search/query tool that retrieves temporal metadata about when content was mentioned in memory files. It has no side effects—it only reads and returns timestamped search results. This is a classic Read category operation with low severity since it cannot alter data or trigger external operations.
From the tool's definition Tool description states 'Temporal search - find when something was mentioned' and 'Searches for content and returns results with temporal context.' The args include a file path and query, with returns showing 'Results with timestamps.' No modification,…
Attacks that exploit this kind of access
Temporal search - find when something was mentioned. Searches for content and returns results with temporal context. Args: file: Path to the .mv2 memory file query: Time-related search query limit: Maximum results (default: 10) Returns: Results with timestamps showing when topics were mentioned. 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_when: 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_when 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_when 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_when. 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_when 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 →