Remove depth maps from the active chunk to free memory.
AI agents call clear_depth_maps 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.
The tool permanently deletes depth maps, which are valuable intermediate computational products in a photogrammetry workflow. Unlike reversible Write operations, depth maps cannot be recovered once cleared—they must be regenerated from scratch through expensive reprocessing (e.g., re-running depth estimation algorithms). An AI agent misusing this could destroy hours of processing work.
From the tool's definition Tool name 'clear_depth_maps' combined with description 'Remove depth maps from the active chunk to free memory' indicates irreversible deletion of computed depth map data.
Documented attack patterns abuse exactly the kind of access clear_depth_maps 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_depth_maps:
{
"version": "1",
"default": "deny",
"hide": [
"clear_depth_maps"
]
}clear_depth_maps 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 depth maps 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_depth_maps: 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_depth_maps 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_depth_maps 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_depth_maps. 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_depth_maps 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.