AI agents use duplicate_chunk to create or update resources in Metashape MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Metashape MCP Server environment.
Duplicating a chunk creates a copy of project data within Metashape, which is a reversible, non-destructive Write operation. The original chunk remains intact. While it modifies project state (increases disk/memory usage), the action is recoverable by deletion. Not Destructive because nothing is deleted or overwritten irreversibly.
From the tool's definition Tool named 'duplicate_chunk' in a photogrammetry/3D modeling system. Duplicates a chunk (a project component in Metashape containing photos, cameras, and reconstruction data). Description is empty, lowering confidence slightly.
Documented attack patterns abuse exactly the kind of access duplicate_chunk 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 duplicate_chunk:
{
"version": "1",
"default": "deny",
"tools": {
"duplicate_chunk": {
"limits": [
{
"counter": "duplicate_chunk_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} duplicate_chunk stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
duplicate_chunk. It is categorised as a Write tool in the Metashape MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Metashape MCP Server MCP server in PolicyLayer and add a rule for duplicate_chunk: 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.
duplicate_chunk is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the duplicate_chunk 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 duplicate_chunk. 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.
duplicate_chunk 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.