statistical_outlier_removal · Cloudcompare MCP

WHAT IT DOES

What statistical_outlier_removal does on Cloudcompare

AI agents use statistical_outlier_removal 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 statistical_outlier_removal needs a policy

The tool modifies point cloud data by removing outlier points, which is a data transformation/filtering operation. While it removes data, this is a standard reversible processing step (original file is not necessarily overwritten; a filtered version is produced), placing it in Write rather than Destructive. Severity is medium because misapplication could corrupt valuable 3D data by removing legitimate points.

From the tool's definition Remove statistical outliers (SOR filter)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

statistical_outlier_removal Rate-limited

statistical_outlier_removal 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": {
    "statistical_outlier_removal": {
      "limits": [
        {
          "counter": "statistical_outlier_removal_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 statistical_outlier_removal

What does the statistical_outlier_removal tool do? +

Remove statistical outliers (SOR filter). 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 statistical_outlier_removal? +

Register the Cloudcompare MCP server in PolicyLayer and add a rule for statistical_outlier_removal: 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 statistical_outlier_removal? +

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

Can I rate-limit statistical_outlier_removal? +

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

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

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