Add an entire directory to the code graph without clearing existing data. USE WHEN: you need to explore a new codebase (e.g., kernel headers, another driver's source) alongside already-indexed code. Recursively indexes all supported files, resolves cross-file imports, and rebuilds search indexes....
Risk signalsAccepts file system path (path) · Bulk/mass operation — affects multiple targets
Part of the Codegraph server.
Free to start. No card required.
AI agents may call codegraph_index_directory to permanently remove or destroy resources in Codegraph. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call codegraph_index_directory in a loop, permanently destroying resources in Codegraph. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
{
"version": "1",
"default": "deny",
"hide": [
"codegraph_index_directory"
]
}See the full Codegraph policy for all 38 tools.
These attack patterns abuse exactly the kind of access codegraph_index_directory gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
Add an entire directory to the code graph without clearing existing data. USE WHEN: you need to explore a new codebase (e.g., kernel headers, another driver's source) alongside already-indexed code. Recursively indexes all supported files, resolves cross-file imports, and rebuilds search indexes. Does NOT clear existing graph data — new files are added alongside. Set embed=true to also build embeddings for similarity tools. Requires path parameter (absolute directory path).. It is categorised as a Destructive tool in the Codegraph MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Codegraph MCP server in PolicyLayer and add a rule for codegraph_index_directory: 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 Codegraph. Nothing to install.
codegraph_index_directory is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the codegraph_index_directory 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_directory. 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_directory is provided by the Codegraph MCP server (codegraph-ai/CodeGraph). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 38 Codegraph tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.