filter_by_scalar_field · Cloudcompare MCP: Risk & Policy

WHAT IT DOES

What filter_by_scalar_field does on Cloudcompare

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

This tool filters a point cloud by retaining only points within a specified scalar field range, effectively modifying the dataset by removing points outside the range. This is a Write operation (creates a filtered/modified version of the cloud) rather than Destructive since the original data is typically preserved and the operation produces a new filtered result.

From the tool's definition Keep only points with scalar-field value in [min_val, max_val]

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

filter_by_scalar_field Rate-limited

filter_by_scalar_field 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": {
    "filter_by_scalar_field": {
      "limits": [
        {
          "counter": "filter_by_scalar_field_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 filter_by_scalar_field

What does the filter_by_scalar_field tool do? +

Keep only points with scalar-field value in [min_val, max_val]. 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 filter_by_scalar_field? +

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

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

Can I rate-limit filter_by_scalar_field? +

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

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

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