Store a memory with file citations. Snippets are auto-extracted.
AI agents use vrm_store to create or update resources in Verified Repo Memory — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Verified Repo Memory environment.
vrm_store creates/writes new memory entries with citations into the repository-scoped memory system. This is a reversible write operation (a sibling tool vrm_forget exists for removal). Misuse could lead to storing incorrect or misleading information, but it does not execute code, delete data, or involve finances.
From the tool's definition 'Store a memory with file citations. Snippets are auto-extracted.'
Attacks that exploit this kind of access
Store a memory with file citations. Snippets are auto-extracted. It is categorised as a Write tool in the Verified Repo Memory MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Verified Repo Memory MCP server in PolicyLayer and add a rule for vrm_store: 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_store is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the vrm_store 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_store. 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_store 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 →