AI agents use update_transform 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.
The tool updates (modifies) data reversibly within the Metashape project. Transformation matrices control spatial positioning of 3D models and point clouds. While this affects 3D geometry output, it does not execute arbitrary code, delete data, or trigger financial transactions. The impact is reversible—transforms can be re-adjusted or undone.
From the tool's definition Tool description states 'Update the chunk transformation matrix' — this modifies the transformation parameters of a photogrammetry chunk, affecting 3D positioning and alignment without deletion.
Documented attack patterns abuse exactly the kind of access update_transform 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 update_transform:
{
"version": "1",
"default": "deny",
"tools": {
"update_transform": {
"limits": [
{
"counter": "update_transform_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} update_transform 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.
Update the chunk transformation matrix. 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 update_transform: 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.
update_transform 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 update_transform 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 update_transform. 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.
update_transform 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.