Remove the dense point cloud from the active chunk to free memory.
AI agents call clear_point_cloud to permanently remove resources in Metashape MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes the dense point cloud data from the active chunk. While the source photos remain, the processed 3D point cloud data is lost and would require significant computational resources to regenerate. This is an irreversible action that destroys work product, fitting the Destructive category.
From the tool's definition Tool name 'clear_point_cloud' and description 'Remove the dense point cloud from the active chunk to free memory' indicates irreversible deletion of computed data.
Documented attack patterns abuse exactly the kind of access clear_point_cloud gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Metashape MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for clear_point_cloud:
{
"version": "1",
"default": "deny",
"hide": [
"clear_point_cloud"
]
} clear_point_cloud disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove the dense point cloud from the active chunk to free memory. It is categorised as a Destructive tool in the Metashape MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Metashape MCP Server MCP server in PolicyLayer and add a rule for clear_point_cloud: 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 Metashape MCP Server. Nothing to install.
clear_point_cloud is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the clear_point_cloud 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 clear_point_cloud. 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.
clear_point_cloud is provided by the Metashape MCP Server MCP server (jenkinsm13/metashape-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Metashape MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
112 Metashape MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.