AI agents invoke codegraph_index to trigger actions in Musubix. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
While the tool does not delete data or move money, it executes a non-trivial computational operation that analyzes and processes code. It reads code but goes beyond simple retrieval by performing extraction and relationship mapping. This active processing of external systems places it in the Execute category rather than Read.
From the tool's definition The tool 'codegraph_index' performs indexing of code repositories by extracting and analyzing entities and relationships.
Attacks that exploit this kind of access
Index a code repository or directory to build a code graph. This extracts entities (classes, functions, etc.) and their relationships. It is categorised as a Execute tool in the Musubix MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Musubix MCP server in PolicyLayer and add a rule for codegraph_index: 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_index is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the codegraph_index 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_index. 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_index 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 →