remove_points_by_class

THE RISK

Critical Risk

Why remove_points_by_class needs a policy

This tool removes point cloud data by classification, which is irreversible. Once points are deleted from a 3D model in Metashape, they cannot be recovered without reprocessing. This qualifies as Destructive rather than Write. The high severity reflects the potential loss of significant photogrammetry work products.

From the tool's definition Tool name 'remove_points_by_class' explicitly indicates deletion/removal of point cloud data. No description provided, but the verb 'remove' in a photogrammetry context (alongside sibling tools like 'add_marker', 'align_cameras', 'build_contours') strongly…

Documented attack patterns abuse exactly the kind of access remove_points_by_class gives an agent:

POLICY

How to control remove_points_by_class

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 remove_points_by_class:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_points_by_class"
  ]
}

remove_points_by_class disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Metashape MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Metashape MCP Server tools

Destructive clean_model Remove model artifacts based on filtering criteria. Destructive clear_dem Remove the DEM from the active chunk to free memory. Destructive clear_depth_maps Remove depth maps from the active chunk to free memory. Destructive clear_masks Remove masks from cameras. Destructive clear_model Remove the 3D model from the active chunk to free memory. Destructive clear_orthomosaic Remove the orthomosaic from the active chunk to free memory. Destructive clear_point_cloud Remove the dense point cloud from the active chunk to free memory. Destructive clear_tiled_model Remove the tiled model from the active chunk to free memory.

All 112 Metashape MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Metashape MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about remove_points_by_class

What does the remove_points_by_class tool do? +

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

How do I enforce a policy on remove_points_by_class? +

Register the Metashape MCP Server MCP server in PolicyLayer and add a rule for remove_points_by_class: 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.

What risk level is remove_points_by_class? +

remove_points_by_class is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_points_by_class? +

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

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

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

Enforce policy on every Metashape MCP Server tool call.

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.

CHECK YOUR STACK →