List all active folder watchers.
AI agents call list_watchers to retrieve information from ChromaDB Local MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and enumerates existing folder watcher configurations. It performs no creation, modification, deletion, code execution, or financial operations. The worst-case misuse would be information disclosure about which directories are being monitored, which is a low-severity read-only risk.
From the tool's definition Tool name 'list_watchers' and description 'List all active folder watchers' indicate a query operation that retrieves and displays current watcher status with no modification or side effects.
Attacks that exploit this kind of access
List all active folder watchers. It is categorised as a Read tool in the ChromaDB Local MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ChromaDB Local MCP Server MCP server in PolicyLayer and add a rule for list_watchers: 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.
list_watchers is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_watchers 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.
Set action: deny in the PolicyLayer policy for list_watchers. 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.
list_watchers 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →