AI agents use import_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.
Importing a model creates or adds data to the Metashape project, which is a reversible write operation. It does not execute arbitrary code, delete data irreversibly, or move financial resources. The empty description lowers confidence slightly, but the tool name and context of reversible data modification within a photogrammetry workflow support Write classification.
From the tool's definition Tool name 'import_model' indicates importing external 3D model data into Metashape. The sibling tools (add_chunk, add_photos, add_marker, add_scalebar) show this server performs reversible modifications to photogrammetry projects.
Documented attack patterns abuse exactly the kind of access import_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 import_model:
{
"version": "1",
"default": "deny",
"tools": {
"import_model": {
"limits": [
{
"counter": "import_model_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} import_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.
import_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 import_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.
import_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 import_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 import_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.
import_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.