generate_virtual_checkpoints

THE RISK

Low Risk

Why generate_virtual_checkpoints needs a policy

The description is empty, so classification relies solely on the name. 'Generate virtual checkpoints' in a photogrammetry context likely creates reference/validation points in a 3D project (a Write operation), but without a description it's unclear whether this has side effects, modifies data, or is purely analytical. Confidence is low due to lack of description.

From the tool's definition Tool name is 'generate_virtual_checkpoints'; description is empty or uninformative.

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

POLICY

How to control generate_virtual_checkpoints

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "generate_virtual_checkpoints": {
      "limits": [
        {
          "counter": "generate_virtual_checkpoints_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

generate_virtual_checkpoints gets a rate cap, and 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.

SET A RULE FOR 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 →

Other tools on other servers

Android Forensics ADB MCP Server generate_app_analysis_report Ethereum Tools add Math MCP Server complex_analysis_suite Crypto_MCP aes_encrypt

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Tool risk categories → How PolicyLayer classifies MCP tools by what they can do.
MCP tool → What an MCP tool is and how clients discover and call it.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about generate_virtual_checkpoints

What does the generate_virtual_checkpoints tool do? +

generate_virtual_checkpoints. It is categorised as a Other tool in the Metashape MCP Server MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on generate_virtual_checkpoints? +

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

generate_virtual_checkpoints is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit generate_virtual_checkpoints? +

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

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

generate_virtual_checkpoints 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 →