AI agents call codegraph_local_search to retrieve information from Musubix without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs code search and analysis to understand relationships and context within a codebase. It retrieves information without altering data, executing code, or triggering external operations. The verb 'search' and purpose of 'understanding context' confirm it is a Read operation with minimal risk.
From the tool's definition Tool name 'codegraph_local_search' and description 'Search for related code around a specific entity. Best for understanding how a particular piece of code fits into its context' indicate a search/retrieval operation with no modification or execution.
Attacks that exploit this kind of access
Search for related code around a specific entity. Best for understanding how a particular piece of code fits into its context. It is categorised as a Read tool in the Musubix MCP Server, which means it retrieves data without modifying state.
Register the Musubix MCP server in PolicyLayer and add a rule for codegraph_local_search: 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 Musubix. Nothing to install.
codegraph_local_search 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 codegraph_local_search 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 codegraph_local_search. 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.
codegraph_local_search is provided by the Musubix MCP server (@nahisaho/musubix-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →