List memories by status.
AI agents call vrm_list to retrieve information from Verified Repo Memory without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple listing operation that queries stored memories and returns results grouped by status. There are no side effects, no data modification, no code execution, and no irreversible actions. It is purely informational and falls squarely within the Read category. The low severity reflects minimal risk if misused by an agent—the worst outcome would be enumeration of stored memory state.
From the tool's definition Tool name 'vrm_list' and description 'List memories by status' indicate a read-only operation that retrieves/queries existing data without modification or execution.
Attacks that exploit this kind of access
List memories by status. It is categorised as a Read tool in the Verified Repo Memory MCP Server, which means it retrieves data without modifying state.
Register the Verified Repo Memory MCP server in PolicyLayer and add a rule for vrm_list: 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 Verified Repo Memory. Nothing to install.
vrm_list 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 vrm_list 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 vrm_list. 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.
vrm_list is provided by the Verified Repo Memory MCP server (cognitivemyriad/mcp-verified-repo-memory). 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 →