store_context · ChromaDB Local MCP Server MCP: Risk & Policy

WHAT IT DOES

What store_context does on ChromaDB Local MCP Server

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

WHY IT NEEDS A POLICY

Why store_context needs a policy

The tool creates/writes new data to a local ChromaDB vector store and syncs it to a remote instance. This is a write operation with no indication of irreversible deletion or financial impact. The sync-to-remote aspect slightly increases the blast radius since data propagates beyond the local system, warranting a medium severity.

From the tool's definition Store new context in ChromaDB (stores locally and syncs to remote)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

store_context Rate-limited

store_context 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": {
    "store_context": {
      "limits": [
        {
          "counter": "store_context_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 ChromaDB Local MCP Server, so you can run agents against it safely.

FAQ

Questions about store_context

What does the store_context tool do? +

Store new context in ChromaDB (stores locally and syncs to remote). It is categorised as a Write tool in the ChromaDB Local MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on store_context? +

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

What risk level is store_context? +

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

Can I rate-limit store_context? +

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

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

store_context is provided by the ChromaDB Local MCP Server MCP server (vespo92/chromadblocal-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.