Read a point cloud file natively (no CloudCompare required) and return
AI agents call read_cloud_metadata to retrieve information from Cloudcompare without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries metadata from point cloud files without side effects. It is a passive data retrieval operation that does not create, modify, delete, or execute code. The 'read' action and metadata-only return clearly place it in the Read category with low severity.
From the tool's definition Tool name includes 'read' and description explicitly states 'Read a point cloud file' with return of metadata only. No modification, deletion, or execution of external commands indicated.
Attacks that exploit this kind of access
Read a point cloud file natively (no CloudCompare required) and return. It is categorised as a Read tool in the Cloudcompare MCP Server, which means it retrieves data without modifying state.
Register the Cloudcompare MCP server in PolicyLayer and add a rule for read_cloud_metadata: 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.
read_cloud_metadata is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the read_cloud_metadata 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.
Set action: deny in the PolicyLayer policy for read_cloud_metadata. 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.
read_cloud_metadata 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →