setup_chroma_db · MCP: Risk & Policy

WHAT IT DOES

What setup_chroma_db does on Mcp

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

WHY IT NEEDS A POLICY

Why setup_chroma_db needs a policy

The name 'setup_chroma_db' strongly implies initialization or configuration of a ChromaDB instance — creating collections, indexes, or schemas. This is most likely a Write operation (creating/configuring a database). However, setup could also involve destructive actions like dropping and recreating collections. With an empty description, confidence is lowered.

From the tool's definition Tool name 'setup_chroma_db' and server description mentions 'vector database management' with ChromaDB; description is empty.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

setup_chroma_db Rate-limited

setup_chroma_db 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": {
    "setup_chroma_db": {
      "limits": [
        {
          "counter": "setup_chroma_db_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 Mcp, so you can run agents against it safely.

FAQ

Questions about setup_chroma_db

What does the setup_chroma_db tool do? +

setup_chroma_db. It is categorised as a Write tool in the 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 setup_chroma_db? +

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

What risk level is setup_chroma_db? +

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

Can I rate-limit setup_chroma_db? +

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

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

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