Local semantic reference/impact analysis for a function, type, class, variable, property, interface, or import. Anchor exact symbol first with lspGotoDefinition or localSearchCode; scope large repos with includePattern before paging. Use lspCallHierarchy for caller/callee graph questions.
AI agents call lspFindReferences 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 lspFindReferences. Maximum is 5 queries per call. Multiple queries run in parallel. Use the per-query `page` field to navigate through resu |
Parameters from the server's own tool schema.
This tool retrieves and queries information about code references and symbol relationships within a repository. It is purely analytical with no side effects—it does not execute code, modify files, delete data, or trigger external operations.
From the tool's definition Tool performs 'semantic reference/impact analysis' and 'search' operations without modifying data. Description explicitly states it analyzes and finds references to symbols without any write, execute, or destructive operations mentioned.
Risk signalsAccepts URL/endpoint input (queries[].uri) · Accepts file system path (queries[].filePath) · High parameter count (17 properties)
Documented attack patterns abuse exactly the kind of access lspFindReferences 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 lspFindReferences:
{
"version": "1",
"default": "deny",
"tools": {
"lspFindReferences": {}
}
}lspFindReferences 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 reference/impact analysis for a function, type, class, variable, property, interface, or import. Anchor exact symbol first with lspGotoDefinition or localSearchCode; scope large repos with includePattern before paging. Use lspCallHierarchy for caller/callee graph questions. It is categorised as a Read tool in the Octocode MCP - AI Context Platform MCP Server, which means it retrieves data without modifying state.
lspFindReferences 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 lspFindReferences: 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.
lspFindReferences 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 lspFindReferences 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 lspFindReferences. 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.
lspFindReferences 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.