merge_clouds · Cloudcompare MCP: Risk & Policy

WHAT IT DOES

What merge_clouds does on Cloudcompare

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

WHY IT NEEDS A POLICY

Why merge_clouds needs a policy

Merging clouds combines multiple point cloud datasets into one, which modifies data but remains reversible—the original clouds could be recreated or the merge undone. This is less severe than Execute (which could trigger arbitrary operations) or Destructive (which would irreversibly delete data).

From the tool's definition Tool description states 'Merge two or more point clouds.' The merge operation creates a new combined data structure by modifying input clouds, which is a reversible modification (not destructive deletion) consistent with Write-category tools like 'create' or…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

merge_clouds Rate-limited

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

FAQ

Questions about merge_clouds

What does the merge_clouds tool do? +

Merge two or more point clouds. Requires CloudCompare. It is categorised as a Write tool in the Cloudcompare MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on merge_clouds? +

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

What risk level is merge_clouds? +

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

Can I rate-limit merge_clouds? +

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

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

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