compute_cloud_to_mesh_distances

WHAT IT DOES

What compute_cloud_to_mesh_distances does on Cloudcompare

AI agents invoke compute_cloud_to_mesh_distances 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_cloud_to_mesh_distances needs a policy

This tool runs a CloudCompare computation (an external process) to calculate distances between a point cloud and a mesh. It executes an external operation rather than simply reading stored data or writing new records. The blast radius is medium since it processes potentially large 3D datasets via an external application, but it does not delete data or involve financial transactions.

From the tool's definition 'Compute signed C2M distances from a cloud to a reference mesh. Requires CloudCompare.' — triggers an external CloudCompare operation that processes 3D data

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

compute_cloud_to_mesh_distances Rate-limited

compute_cloud_to_mesh_distances 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_cloud_to_mesh_distances": {
      "limits": [
        {
          "counter": "compute_cloud_to_mesh_distances_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_cloud_to_mesh_distances

What does the compute_cloud_to_mesh_distances tool do? +

Compute signed C2M distances from a cloud to a reference mesh. 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_cloud_to_mesh_distances? +

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

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

Can I rate-limit compute_cloud_to_mesh_distances? +

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

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

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