// MCP TOOL REFERENCE

cortex_code_reindex

ServerCortex Hub
CategoryExecute

WHAT IT DOES

What cortex_code_reindex does on Cortex Hub

AI agents invoke cortex_code_reindex to trigger actions in Cortex Hub. 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.

THE RISK

High Risk

Why cortex_code_reindex needs a policy

This tool executes an external indexing operation (re-index job) on a specified project. While not destructive (the operation is reversible and not financial), it triggers a background process that modifies system state and consumes resources.

From the tool's definition Tool description states it 'Trigger[s] re-indexing of a project' and 'starts a GitNexus re-index job' — these are explicit external operations with side effects that depend on arguments (repo URL, project context).

Documented attack patterns abuse exactly the kind of access cortex_code_reindex gives an agent:

POLICY

How to control cortex_code_reindex

PolicyLayer is an MCP gateway — it sits between your AI agents and Cortex Hub, and nothing reaches the server without passing your rules. This is the rule we recommend for cortex_code_reindex:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cortex_code_reindex": {
      "limits": [
        {
          "counter": "cortex_code_reindex_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

cortex_code_reindex 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.

Create a free account and register Cortex Hub — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Cortex Hub tools

Execute cortex_cypher Run Cypher queries directly against the GitNexus knowledge graph. Supports MATCH, RETURN, Write cortex_session_start Start a new execution session with optional agent identity metadata. Write cortex_knowledge_store Store a knowledge document in the Cortex knowledge base. Auto-chunks and embeds the conten Write cortex_memory_store Store a memory for an AI agent. Memories persist across sessions and can be recalled by se Write cortex_session_end Close a session with a summary of work done. Reports session duration and compliance. Write cortex_task_accept Accept an assigned task, signaling that work will begin. Updates task status to accepted. Write cortex_task_create Create a task and optionally assign it to another agent. Use for delegating work, tracking Write cortex_task_submit_strategy Submit a task execution strategy for user review. The Lead Agent calls this after analyzin

All 25 Cortex Hub tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Cortex Hub → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about cortex_code_reindex

What does the cortex_code_reindex tool do? +

Trigger re-indexing of a project after code changes. Looks up the project by repo URL and starts a GitNexus re-index job. Call this after pushing significant code changes to keep code intelligence up-to-date. It is categorised as a Execute tool in the Cortex Hub MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on cortex_code_reindex? +

Register the Cortex Hub MCP server in PolicyLayer and add a rule for cortex_code_reindex: 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 Cortex Hub. Nothing to install.

What risk level is cortex_code_reindex? +

cortex_code_reindex is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit cortex_code_reindex? +

Yes. Add a rate_limit block to the cortex_code_reindex 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.

How do I block cortex_code_reindex completely? +

Set action: deny in the PolicyLayer policy for cortex_code_reindex. 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.

What MCP server provides cortex_code_reindex? +

cortex_code_reindex is provided by the Cortex Hub MCP server (lktiep/cortex-hub). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Cortex Hub tool call.

Start from Cortex Hub, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

25 Cortex Hub tools catalogued and risk-classified — across an index of 43,000+ MCP servers.