Return a symbol definition with incoming callers/references, outgoing callees/imports, related tests, and process placeholders from Lore
AI agents call repo.symbol_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.
The tool performs read-only data retrieval from a codebase analysis system (Lore). It returns symbol metadata, references, and related information without creating, modifying, deleting, or executing code. The verb 'Return' and the nature of fetching definition/reference data are characteristic of Read category operations.
From the tool's definition Tool description states it 'Return[s] a symbol definition with incoming callers/references, outgoing callees/imports, related tests, and process placeholders' — purely retrieval operations that query and fetch context about code symbols without modifying any…
Attacks that exploit this kind of access
Return a symbol definition with incoming callers/references, outgoing callees/imports, related tests, and process placeholders from Lore. 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 repo.symbol_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.
repo.symbol_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 repo.symbol_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 repo.symbol_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.
repo.symbol_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 →