AI agents use export_model 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.
Export operations create or serialize data artifacts (3D models, imagery) to disk or external formats. While the description is empty, the tool name and server purpose clearly indicate file generation. This is reversible (exported files can be deleted, regenerated, or overwritten), so it falls under Write rather than Destructive.
From the tool's definition Tool name 'export_model' combined with server context describing photogrammetry and 3D model generation. The sibling tools include write operations like 'add_chunk', 'add_marker', 'add_photos' which establish this as a data manipulation server.
Documented attack patterns abuse exactly the kind of access export_model 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 export_model:
{
"version": "1",
"default": "deny",
"tools": {
"export_model": {
"limits": [
{
"counter": "export_model_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}export_model 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.
export_model. 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 export_model: 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.
export_model 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 export_model 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 export_model. 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.
export_model 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.