Reverse-index lookup: all symbols in the vault that reference the given target symbol. Same shape as incoming[] from code.context but exposed as a top-level tool.
AI agents call code.references 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 retrieves and queries existing reference data from a code vault without side effects. It is a pure read operation that returns symbol relationship information. The low severity reflects that misuse would only expose code structure information, not enable destructive or financial actions.
From the tool's definition Tool performs 'Reverse-index lookup' of symbol references; described as exposing data 'in the same shape as incoming[] from code.context' which is a read operation. No modification, deletion, or execution is performed.
Attacks that exploit this kind of access
Reverse-index lookup: all symbols in the vault that reference the given target symbol. Same shape as incoming[] from code.context but exposed as a top-level tool. 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.references: 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.references 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.references 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.references. 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.references 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 →