indexfoundry_index_upsert · IndexFoundry MCP: Risk & Policy

WHAT IT DOES

What indexfoundry_index_upsert does on IndexFoundry MCP

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

WHY IT NEEDS A POLICY

Why indexfoundry_index_upsert needs a policy

Upsert is a standard Write operation—it creates new records or updates existing ones reversibly without permanent deletion. The tool modifies data in vector databases but does not delete, destroy, or cause irreversible effects.

From the tool's definition Tool name contains 'upsert' which is a create-or-update operation; description explicitly states 'Upsert vectors to a vector database' indicating reversible modification of data in external storage systems (Pinecone, Weaviate, Qdrant, Milvus, Chroma).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

indexfoundry_index_upsert Rate-limited

indexfoundry_index_upsert 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": {
    "indexfoundry_index_upsert": {
      "limits": [
        {
          "counter": "indexfoundry_index_upsert_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 IndexFoundry MCP, so you can run agents against it safely.

FAQ

Questions about indexfoundry_index_upsert

What does the indexfoundry_index_upsert tool do? +

Upsert vectors to a vector database. Supports local file-based storage and external providers (Pinecone, Weaviate, Qdrant, Milvus, Chroma). It is categorised as a Write tool in the IndexFoundry MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on indexfoundry_index_upsert? +

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

What risk level is indexfoundry_index_upsert? +

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

Can I rate-limit indexfoundry_index_upsert? +

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

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

indexfoundry_index_upsert is provided by the IndexFoundry MCP server (mnehmos/mnehmos.index-foundry.mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.