AI agents invoke reindex_repository to trigger actions in CodeGraphMCPServer. 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.
This tool executes a potentially long-running, resource-intensive operation that modifies the internal state of the code analysis index. While not destructive (the source repository is unchanged), it is an Execute-category tool because it triggers an external operation whose effects depend on repository contents and could consume significant system resources.
From the tool's definition Tool name: 'reindex_repository'; description: 'Trigger repository re-indexing'. The verb 'Trigger' and 're-indexing' indicate the tool initiates a computational operation on the repository state.
Documented attack patterns abuse exactly the kind of access reindex_repository gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CodeGraphMCPServer, and nothing reaches the server without passing your rules. This is the rule we recommend for reindex_repository:
{
"version": "1",
"default": "deny",
"tools": {
"reindex_repository": {
"limits": [
{
"counter": "reindex_repository_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}reindex_repository stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Trigger repository re-indexing. It is categorised as a Execute tool in the CodeGraphMCPServer MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the CodeGraphMCPServer MCP server in PolicyLayer and add a rule for reindex_repository: 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 CodeGraphMCPServer. Nothing to install.
reindex_repository 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 reindex_repository 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 reindex_repository. 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.
reindex_repository is provided by the CodeGraphMCPServer MCP server (nahisaho/codegraphmcpserver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CodeGraphMCPServer, 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.
14 CodeGraphMCPServer tools catalogued and risk-classified — across an index of 43,000+ MCP servers.