AI agents invoke build_dem to trigger actions in Metashape MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool performs a computational execution that triggers Metashape's DEM (Digital Elevation Model) generation pipeline. While the description is empty, context from the server's purpose (AI-powered automation of photogrammetry tasks) and sibling tools clearly indicate this executes a complex processing operation.
From the tool's definition Tool name 'build_dem' (Build Digital Elevation Model) on a photogrammetry automation server that enables control of complex 3D processing tasks. Sibling tools like 'build_contours', 'align_cameras', and 'align_chunks' are all computational operations.
Documented attack patterns abuse exactly the kind of access build_dem 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 build_dem:
{
"version": "1",
"default": "deny",
"tools": {
"build_dem": {
"limits": [
{
"counter": "build_dem_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}build_dem 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.
Free to start. No card required.
build_dem. 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.
Register the Metashape MCP Server MCP server in PolicyLayer and add a rule for build_dem: 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.
build_dem is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the build_dem 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 build_dem. 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.
build_dem 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.