Local semantic call-flow navigation: incoming callers or outgoing callees of a function/method. Anchor with localSearchCode or a prior lspGotoDefinition result first. Use lspFindReferences for non-call usages (types, imports, assignments).
AI agents call lspCallHierarchy to retrieve information from Octocode MCP - AI Context Platform without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
queries | array | Yes | Array of queries for lspCallHierarchy. Maximum is 5 queries per call. Multiple queries run in parallel. Use the per-query `page` field to navigate through resul |
Parameters from the server's own tool schema.
This tool retrieves and displays code relationship information (call hierarchies) without creating, modifying, deleting, or executing any code. It is purely an analytical read operation on local code structure, similar to a code search or reference finder. The low severity reflects minimal risk even if misused by an AI agent, as it only returns information about existing code relationships.
From the tool's definition Tool performs 'Local semantic call-flow navigation: incoming callers or outgoing callees of a function/method' - this is a retrieval and analysis operation that examines code structure without modifying anything.
Risk signalsAccepts URL/endpoint input (queries[].uri) · Accepts file system path (queries[].filePath) · High parameter count (15 properties)
Documented attack patterns abuse exactly the kind of access lspCallHierarchy gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Octocode MCP - AI Context Platform, and nothing reaches the server without passing your rules. This is the rule we recommend for lspCallHierarchy:
{
"version": "1",
"default": "deny",
"tools": {
"lspCallHierarchy": {}
}
}lspCallHierarchy 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.
Local semantic call-flow navigation: incoming callers or outgoing callees of a function/method. Anchor with localSearchCode or a prior lspGotoDefinition result first. Use lspFindReferences for non-call usages (types, imports, assignments). It is categorised as a Read tool in the Octocode MCP - AI Context Platform MCP Server, which means it retrieves data without modifying state.
lspCallHierarchy accepts 1 parameter: queries. Required: queries. The full parameter table on this page comes from the server's own tool schema.
Register the Octocode MCP - AI Context Platform MCP server in PolicyLayer and add a rule for lspCallHierarchy: 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 Octocode MCP - AI Context Platform. Nothing to install.
lspCallHierarchy 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 lspCallHierarchy 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 lspCallHierarchy. 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.
lspCallHierarchy is provided by the Octocode MCP - AI Context Platform MCP server (octocode-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Octocode MCP - AI Context Platform, 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.
13 Octocode MCP - AI Context Platform tools catalogued and risk-classified — across an index of 43,000+ MCP servers.