stop_watch · ChromaDB Local MCP Server MCP: Risk & Policy

WHAT IT DOES

What stop_watch does on ChromaDB Local MCP Server

AI agents invoke stop_watch to trigger actions in ChromaDB Local MCP Server. 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 stop_watch needs a policy

This tool terminates an active folder-watching/monitoring process. It executes a state change by stopping a running background process. It is not simply reading data, nor does it create/modify/delete data directly. It triggers an external operation (stopping a file watcher daemon or process), placing it in the Execute category.

From the tool's definition Stop watching a folder

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_watch Rate-limited

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

FAQ

Questions about stop_watch

What does the stop_watch tool do? +

Stop watching a folder. It is categorised as a Execute tool in the ChromaDB Local MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on stop_watch? +

Register the ChromaDB Local MCP Server MCP server in PolicyLayer and add a rule for stop_watch: 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 stop_watch? +

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

Can I rate-limit stop_watch? +

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

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

stop_watch 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.