rebuild_vector_index · Scifinder Route MCP: Risk & Policy

WHAT IT DOES

What rebuild_vector_index does on Scifinder Route

AI agents invoke rebuild_vector_index to trigger actions in Scifinder Route. 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 rebuild_vector_index needs a policy

This tool executes an external operation (calls an embedding endpoint) to generate and rebuild a vector index. It is not a simple read, nor does it delete data, but it does trigger computation and likely overwrites or regenerates the existing vector index, making it an Execute action. Misuse could corrupt or invalidate the search index, warranting medium severity.

From the tool's definition 'Generate embeddings for reaction steps using the configured embedding endpoint' — triggers an external embedding endpoint operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rebuild_vector_index Rate-limited

rebuild_vector_index 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": {
    "rebuild_vector_index": {
      "limits": [
        {
          "counter": "rebuild_vector_index_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 Scifinder Route, so you can run agents against it safely.

FAQ

Questions about rebuild_vector_index

What does the rebuild_vector_index tool do? +

Generate embeddings for reaction steps using the configured embedding endpoint. It is categorised as a Execute tool in the Scifinder Route MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on rebuild_vector_index? +

Register the Scifinder Route MCP server in PolicyLayer and add a rule for rebuild_vector_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 Scifinder Route. Nothing to install.

What risk level is rebuild_vector_index? +

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

Can I rate-limit rebuild_vector_index? +

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

How do I block rebuild_vector_index completely? +

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

What MCP server provides rebuild_vector_index? +

rebuild_vector_index is provided by the Scifinder Route MCP server (kettly1260/scifinder-route-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.