build_depth_maps

THE RISK

High Risk

Why build_depth_maps needs a policy

Build_depth_maps triggers a significant external computational operation in Metashape that processes image data to generate 3D depth information. The effects depend entirely on supplied arguments (which photos, processing parameters). This cannot be undone without manual intervention and represents automation of a complex external task, fitting the Execute category.

From the tool's definition Tool name 'build_depth_maps' indicates execution of a computational photogrammetry operation (depth map generation).

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

POLICY

How to control build_depth_maps

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "build_depth_maps": {
      "limits": [
        {
          "counter": "build_depth_maps_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

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.

RATE-LIMIT 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 →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Metashape MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-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.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about build_depth_maps

What does the build_depth_maps tool do? +

build_depth_maps. It is categorised as a Execute tool in the Metashape MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on build_depth_maps? +

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

What risk level is build_depth_maps? +

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

Can I rate-limit build_depth_maps? +

Yes. Add a rate_limit block to the build_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.

How do I block build_depth_maps completely? +

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

What MCP server provides build_depth_maps? +

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

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 →