Given a fully-qualified symbol name, returns the symbol metadata plus all incoming references (callers/importers) and outgoing references (callees/imports).
AI agents call code.context 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 performs read-only analysis of code relationships and metadata. It retrieves information about symbol definitions, callers, and dependencies without executing code, modifying data, or triggering external operations. The blast radius of misuse is minimal since it only exposes structural information about code that could already be accessed through static analysis.
From the tool's definition Tool description states it 'returns the symbol metadata plus all incoming references and outgoing references' — purely retrieval and querying of code structure data with no modification or execution.
Attacks that exploit this kind of access
Given a fully-qualified symbol name, returns the symbol metadata plus all incoming references (callers/importers) and outgoing references (callees/imports). 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.context: 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.context 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.context 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.context. 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.context 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 →