run_cloudcompare_command · Cloudcompare MCP: Risk & Policy

WHAT IT DOES

What run_cloudcompare_command does on Cloudcompare

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

This tool permits execution of arbitrary CloudCompare CLI commands with user-supplied arguments, making it an Execute category risk. The blast radius is high because an AI agent could invoke CloudCompare operations beyond the scope of the sibling read/write tools (e.g., shell command injection, resource exhaustion, or unintended file system operations), though it is not Destructive by default since CloudCompare CLI…

From the tool's definition Tool description states 'Run an arbitrary CloudCompare CLI command' — the word 'arbitrary' indicates the tool accepts unrestricted command arguments to an external application (CloudCompare CLI).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_cloudcompare_command Rate-limited

run_cloudcompare_command 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": {
    "run_cloudcompare_command": {
      "limits": [
        {
          "counter": "run_cloudcompare_command_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 run_cloudcompare_command

What does the run_cloudcompare_command tool do? +

Run an arbitrary CloudCompare CLI command. 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 run_cloudcompare_command? +

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

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

Can I rate-limit run_cloudcompare_command? +

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

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

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