ambiance_setup_project

Server Ambiance MCP Server sbarron/ambiancemcp

Category Write

Risk class Medium

Parameters 00 required

WHAT IT DOES

What ambiance_setup_project does on Ambiance MCP Server

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

WHY IT NEEDS A POLICY

Why ambiance_setup_project needs a policy

While this tool does not delete data (ruling out Destructive) or execute arbitrary code directly (ruling out Execute), it does create and modify project configuration, indexing structures, and potentially synchronizes data to external systems.

From the tool's definition The tool performs 'Auto-detect, index, and configure project' with 'file watching for incremental updates' and 'cloud sync'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ambiance_setup_project Rate-limited

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

FAQ

Questions about ambiance_setup_project

What does the ambiance_setup_project tool do? +

⚙️ SETUP PROJECT - Auto-detect, index, and configure project for optimal context retrieval. Handles all the background complexity: project detection, smart indexing with ignore patterns, file watching for incremental updates, and cloud sync (if authenticated). Run this once per project or when you want to refresh the index. It is categorised as a Write tool in the Ambiance 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 ambiance_setup_project? +

Register the Ambiance MCP Server MCP server in PolicyLayer and add a rule for ambiance_setup_project: 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_setup_project? +

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

Can I rate-limit ambiance_setup_project? +

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

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

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