Local ripgrep search for text, regex, imports, identifiers, constants, TODOs, or errors. Start here when a local symbol's location is unknown — results become lineHint anchors for localGetFileContent (via matchString/startLine) and all LSP tools. Use mode='discovery' for cheap presence checks; mo...
AI agents call localSearchCode 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 localSearchCode. Maximum is 5 queries per call. Multiple queries run in parallel. Use the per-query `page` field to navigate through result |
Parameters from the server's own tool schema.
This tool retrieves and searches local code content without altering data. It produces references and location hints ('lineHint anchors') to support downstream analysis, but performs no writes, deletes, or code execution. The 'mode=discovery' and 'mode=detailed' variants both remain read-only query operations.
From the tool's definition Tool description states it performs 'Local ripgrep search for text, regex, imports, identifiers, constants, TODOs, or errors' and 'results become lineHint anchors' for subsequent queries.
Risk signalsAccepts file system path (queries[].path) · High parameter count (34 properties)
Documented attack patterns abuse exactly the kind of access localSearchCode 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 localSearchCode:
{
"version": "1",
"default": "deny",
"tools": {
"localSearchCode": {}
}
}localSearchCode 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 ripgrep search for text, regex, imports, identifiers, constants, TODOs, or errors. Start here when a local symbol's location is unknown — results become lineHint anchors for localGetFileContent (via matchString/startLine) and all LSP tools. Use mode='discovery' for cheap presence checks; mode='detailed' for expanded snippets. Text hits are candidates — verify with LSP for semantic identity. It is categorised as a Read tool in the Octocode MCP - AI Context Platform MCP Server, which means it retrieves data without modifying state.
localSearchCode 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 localSearchCode: 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.
localSearchCode 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 localSearchCode 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 localSearchCode. 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.
localSearchCode 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.