compute_normals · Cloudcompare MCP: Risk & Policy

WHAT IT DOES

What compute_normals does on Cloudcompare

AI agents invoke compute_normals to trigger actions in Cloudcompare. 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 compute_normals needs a policy

This tool runs a computational operation via CloudCompare (an external application) to estimate surface normals on 3D point cloud/mesh data. It executes an external process whose effects depend on the input data. It modifies the in-memory/file representation of point cloud data by adding normal vectors, but the primary risk is executing an external command.

From the tool's definition 'Estimate surface normals' — triggers CloudCompare computational processing on 3D point cloud data, requiring external tool execution ('Requires CloudCompare')

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

compute_normals Rate-limited

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

FAQ

Questions about compute_normals

What does the compute_normals tool do? +

Estimate surface normals. Requires CloudCompare. It is categorised as a Execute tool in the Cloudcompare MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on compute_normals? +

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

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

Can I rate-limit compute_normals? +

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

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

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