Search for candidates (no JIT verification, fast).
AI agents call vrm_search 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 retrieves or queries data from a repository memory store to find matching candidates. It performs no modifications, deletions, or external executions. The emphasis on speed and lack of verification indicates a simple read operation. Classified as Read with low severity, as misuse would only expose existing information without causing irreversible harm or state changes.
From the tool's definition Tool name 'vrm_search' combined with description 'Search for candidates (no JIT verification, fast)' indicates a search/query operation. The phrase 'no JIT verification' and 'fast' suggest this is a retrieval-only operation without side effects.
Attacks that exploit this kind of access
Search for candidates (no JIT verification, fast). 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_search: 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_search 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_search 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_search. 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_search 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 →