ambiance_start_watching · Ambiance MCP Server MCP

WHAT IT DOES

What ambiance_start_watching does on Ambiance MCP Server

AI agents invoke ambiance_start_watching to trigger actions in Ambiance 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 ambiance_start_watching needs a policy

This tool executes a file-watching daemon/process that continuously monitors a directory and triggers indexing operations. While not destructive or financial, it is an Execute-category tool because it launches an external operation (file system monitoring and automatic indexing) whose effects depend on the watched project context.

From the tool's definition Tool description states it will 'Start watching a project for file changes (automatic incremental indexing)' - this initiates a background process that monitors and automatically indexes project files based on file system events.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ambiance_start_watching Rate-limited

ambiance_start_watching 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": {
    "ambiance_start_watching": {
      "limits": [
        {
          "counter": "ambiance_start_watching_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 Ambiance MCP Server, so you can run agents against it safely.

FAQ

Questions about ambiance_start_watching

What does the ambiance_start_watching tool do? +

Start watching a project for file changes (automatic incremental indexing). It is categorised as a Execute tool in the Ambiance 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 ambiance_start_watching? +

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

What risk level is ambiance_start_watching? +

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

Can I rate-limit ambiance_start_watching? +

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

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

ambiance_start_watching is provided by the Ambiance MCP Server MCP server (sbarron/ambiancemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.