get_call_graph
AI agents call get_call_graph to retrieve information from Codebase Contextifier 9000 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Call graphs are data structures representing function/method invocations. Getting a call graph is a retrieval operation that queries indexed code relationships without side effects. This aligns with the Read category for tools that retrieve or query data with no side effects.
From the tool's definition Tool name is 'get_call_graph' and sibling tools like 'find_callees', 'find_callers', 'find_usages', 'get_class_hierarchy', and 'get_graph_statistics' are all clearly Read operations that retrieve code structure information.
Attacks that exploit this kind of access
get_call_graph. It is categorised as a Read tool in the Codebase Contextifier 9000 MCP Server, which means it retrieves data without modifying state.
Register the Codebase Contextifier 9000 MCP server in PolicyLayer and add a rule for get_call_graph: 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 Codebase Contextifier 9000. Nothing to install.
get_call_graph 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 get_call_graph 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 get_call_graph. 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.
get_call_graph is provided by the Codebase Contextifier 9000 MCP server (jarmentor/codebase-contextifier-9000). 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 →