Local semantic jump from usage/import/export/type/member to definition. Use when same-named text matches may collide. Anchor from a localSearchCode result, then follow re-exports/aliases to canonical implementation. Chain to lspFindReferences or lspCallHierarchy after locating the definition.
AI agents call lspGotoDefinition 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 lspGotoDefinition. 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.
lspGotoDefinition is a code navigation utility that resolves symbolic references to their definitions. It retrieves and analyzes code structure to locate definition locations but does not execute code, modify files, delete anything, or create side effects. This is a pure read operation typical of Language Server Protocol (LSP) features used for code comprehension and analysis.
From the tool's definition Tool performs 'semantic jump from usage/import/export/type/member to definition' and 'follow re-exports/aliases to canonical implementation'. These are navigation and lookup operations with no modification, deletion, or execution of code.
Risk signalsAccepts URL/endpoint input (queries[].uri) · Accepts file system path (queries[].filePath) · High parameter count (12 properties)
Documented attack patterns abuse exactly the kind of access lspGotoDefinition 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 lspGotoDefinition:
{
"version": "1",
"default": "deny",
"tools": {
"lspGotoDefinition": {}
}
}lspGotoDefinition 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 jump from usage/import/export/type/member to definition. Use when same-named text matches may collide. Anchor from a localSearchCode result, then follow re-exports/aliases to canonical implementation. Chain to lspFindReferences or lspCallHierarchy after locating the definition. It is categorised as a Read tool in the Octocode MCP - AI Context Platform MCP Server, which means it retrieves data without modifying state.
lspGotoDefinition 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 lspGotoDefinition: 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.
lspGotoDefinition 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 lspGotoDefinition 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 lspGotoDefinition. 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.
lspGotoDefinition 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.