Return deterministic callees of a known function or method symbol. This tool prefers persisted graph call edges and reports explicit degraded-mode receipts when it had to fall back to heuristic extraction.
AI agents call find_callees to retrieve information from Context Engine MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a deterministic lookup in a persisted call graph to retrieve outbound edges (callees) from a given function symbol. It has no side effects—it only reads and reports data from the codebase analysis graph. Even the fallback to 'heuristic extraction' is still a read operation.
From the tool's definition Tool name 'find_callees' and description 'Return deterministic callees of a known function or method symbol' indicate a query operation that retrieves call graph information without modification.
Documented attack patterns abuse exactly the kind of access find_callees gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Context Engine MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for find_callees:
{
"version": "1",
"default": "deny",
"tools": {
"find_callees": {}
}
}find_callees is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Return deterministic callees of a known function or method symbol. This tool prefers persisted graph call edges and reports explicit degraded-mode receipts when it had to fall back to heuristic extraction. It is categorised as a Read tool in the Context Engine MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Context Engine MCP Server MCP server in PolicyLayer and add a rule for find_callees: 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 Context Engine MCP Server. Nothing to install.
find_callees 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 find_callees 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 find_callees. 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.
find_callees is provided by the Context Engine MCP Server MCP server (kirachon/context-engine). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Context Engine MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
50 Context Engine MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.