Return deterministic local callers and/or callees of a known function or method symbol. Use this tool when you need to: - See which functions invoke a given symbol (callers) and where - Inspect which identifiers a function invokes inside its own body (callees) - Complement symbol_definition (sing...
AI agents call call_relationships 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 purely queries and returns static analysis data about call relationships in code. It performs read-only inspection of the codebase to find callers and callees, with no side effects, writes, or destructive actions.
From the tool's definition Return deterministic local callers and/or callees of a known function or method symbol
Documented attack patterns abuse exactly the kind of access call_relationships 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 call_relationships:
{
"version": "1",
"default": "deny",
"tools": {
"call_relationships": {}
}
}call_relationships 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 local callers and/or callees of a known function or method symbol. Use this tool when you need to: - See which functions invoke a given symbol (callers) and where - Inspect which identifiers a function invokes inside its own body (callees) - Complement symbol_definition (single declaration site) and symbol_references (non-declaration usages) Caller heuristic: lines containing <symbol>( that are not declaration-like; the nearest enclosing declaration is reported as callerSymbol when detectable. Callee heuristic: locates the symbol. 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 call_relationships: 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.
call_relationships 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 call_relationships 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 call_relationships. 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.
call_relationships 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.