BFS call-chain subgraph from a given symbol up to the requested depth (1-5). Returns nodes and edges.
AI agents call code.callgraph 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 retrieves call graph information (nodes and edges) starting from a symbol. It performs a breadth-first search traversal to construct a subgraph representation up to a specified depth. No data is created, modified, deleted, or executed—it only reads and analyzes existing code structure relationships. This is a pure read operation with no side effects.
From the tool's definition Tool description: 'BFS call-chain subgraph from a given symbol up to the requested depth (1-5). Returns nodes and edges.' The verb 'Returns' indicates data retrieval without modification.
Attacks that exploit this kind of access
BFS call-chain subgraph from a given symbol up to the requested depth (1-5). Returns nodes and edges. 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.callgraph: 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.callgraph 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.callgraph 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.callgraph. 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.callgraph 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 →