List all code repos indexed in the current vault. The last_indexed_at field is the staleness signal — compute staleness locally as Date.now() - last_indexed_at.
AI agents call code.list_repos to retrieve information from Lore Context without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns a list of indexed code repositories with their metadata. No data is created, modified, deleted, or executed. The staleness computation is a local operation on the client side. The blast radius of misuse is minimal — an agent would only gain knowledge of what repos exist and their indexing status, which is informational. This is a straightforward Read operation.
From the tool's definition Tool name 'code.list_repos' and description 'List all code repos indexed in the current vault' — clearly a retrieval operation with no mutation or side effects. Returns metadata including last_indexed_at timestamp.
Attacks that exploit this kind of access
List all code repos indexed in the current vault. The last_indexed_at field is the staleness signal — compute staleness locally as Date.now() - last_indexed_at. It is categorised as a Read tool in the Lore Context MCP Server, which means it retrieves data without modifying state.
Register the Lore Context MCP server in PolicyLayer and add a rule for code.list_repos: 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 Lore Context. Nothing to install.
code.list_repos 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 code.list_repos 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 code.list_repos. 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.
code.list_repos is provided by the Lore Context MCP server (Lore-Context/lore-context). 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 →