Return deterministic callers of a known function or method symbol. This tool prefers persisted graph call edges and falls back explicitly when graph coverage is unavailable or incomplete. Use when you want call sites for one symbol without the broader combined output of call_relationships.
AI agents call find_callers 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.
The tool retrieves call graph information about existing code symbols without creating, modifying, deleting, or executing anything. It is a read-only query into a codebase graph or index. The blast radius of misuse is minimal—an agent could retrieve information about internal code relationships, but this poses no destructive or operational risk.
From the tool's definition Tool name is 'find_callers' and description states 'Return deterministic callers of a known function or method symbol' — this is purely a query/retrieval operation that 'prefers persisted graph call edges' with no modification, deletion, or execution…
Documented attack patterns abuse exactly the kind of access find_callers 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_callers:
{
"version": "1",
"default": "deny",
"tools": {
"find_callers": {}
}
}find_callers 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 callers of a known function or method symbol. This tool prefers persisted graph call edges and falls back explicitly when graph coverage is unavailable or incomplete. Use when you want call sites for one symbol without the broader combined output of call_relationships. 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_callers: 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_callers 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_callers 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_callers. 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_callers 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.