vectorise_index_project · Vectorise MCP: Risk & Policy

WHAT IT DOES

What vectorise_index_project does on Vectorise

AI agents use vectorise_index_project to create or update resources in Vectorise — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vectorise environment.

WHY IT NEEDS A POLICY

Why vectorise_index_project needs a policy

The tool name strongly implies it creates a new index (project) by ingesting documents into the vector+keyword search store. This is a Write operation — it creates/modifies index data. Since the description is empty, confidence is reduced, but sibling tools like vectorise_reindex_project and vectorise_delete_project suggest this is the initial creation step.

From the tool's definition Tool name: vectorise_index_project; description is empty. Server context: 'indexes folders of documents into a hybrid vector + keyword search index'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

vectorise_index_project Rate-limited

vectorise_index_project stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "vectorise_index_project": {
      "limits": [
        {
          "counter": "vectorise_index_project_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about vectorise_index_project

What does the vectorise_index_project tool do? +

vectorise_index_project. It is categorised as a Write tool in the Vectorise MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on vectorise_index_project? +

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

What risk level is vectorise_index_project? +

vectorise_index_project is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit vectorise_index_project? +

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

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

vectorise_index_project is provided by the Vectorise MCP server (jameslovespancakes/vectorised-embedding-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.