reindex_code_source · Memex MCP: Risk & Policy

WHAT IT DOES

What reindex_code_source does on Memex

AI agents invoke reindex_code_source to trigger actions in Memex. 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.

WHY IT NEEDS A POLICY

Why reindex_code_source needs a policy

The name suggests re-indexing a code source, which implies triggering an operation (rebuilding an index) rather than simply reading or writing data. This is most consistent with Execute, as it likely triggers a background process or scan. However, the empty description significantly lowers confidence. Severity is medium because misuse could corrupt or reset an index, but it is unlikely to be irreversibly destructive.

From the tool's definition Tool name 'reindex_code_source' — description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reindex_code_source Rate-limited

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

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Memex, so you can run agents against it safely.

FAQ

Questions about reindex_code_source

What does the reindex_code_source tool do? +

reindex_code_source. It is categorised as a Execute tool in the Memex MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on reindex_code_source? +

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

What risk level is reindex_code_source? +

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

Can I rate-limit reindex_code_source? +

Yes. Add a rate_limit block to the reindex_code_source 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 reindex_code_source completely? +

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

reindex_code_source is provided by the Memex MCP server (queflyhq/memex). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.