icp_registration · Cloudcompare MCP: Risk & Policy

WHAT IT DOES

What icp_registration does on Cloudcompare

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

ICP (Iterative Closest Point) registration is an algorithm that aligns/transforms one point cloud onto another. This executes a computational operation that modifies the spatial position of the data cloud. It writes transformed output data but primarily involves executing a CloudCompare algorithm/command.

From the tool's definition Register a data cloud onto a model cloud using ICP

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

icp_registration Rate-limited

icp_registration 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": {
    "icp_registration": {
      "limits": [
        {
          "counter": "icp_registration_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 icp_registration

What does the icp_registration tool do? +

Register a data cloud onto a model cloud using ICP. 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 icp_registration? +

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

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

Can I rate-limit icp_registration? +

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

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

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