Download a completed 3D model to local disk with automatic file organization. IMPORTANT: Ask the user which format they need BEFORE downloading. Do NOT download all formats. Format recommendations: GLB (viewing), OBJ (white model printing), 3MF (multicolor printing), FBX (game engines), USDZ (AR)...
AI agents use meshy_download_model to create or update resources in Meshy MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meshy MCP Server environment.
This tool writes files to the local disk (downloads and saves 3D model files with 'smart naming and history tracking'). It creates/writes new files on the filesystem, which is a Write operation. It is not Destructive as it doesn't delete data, not Execute as it doesn't run code, and not Read-only as it has side effects (file creation on disk).
From the tool's definition Download a completed 3D model to local disk with automatic file organization
Documented attack patterns abuse exactly the kind of access meshy_download_model gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Meshy MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for meshy_download_model:
{
"version": "1",
"default": "deny",
"tools": {
"meshy_download_model": {
"limits": [
{
"counter": "meshy_download_model_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} meshy_download_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.
Download a completed 3D model to local disk with automatic file organization. IMPORTANT: Ask the user which format they need BEFORE downloading. Do NOT download all formats. Format recommendations: GLB (viewing), OBJ (white model printing), 3MF (multicolor printing), FBX (game engines), USDZ (AR). By default, files are auto-saved to meshy_output/ under the current working directory with smart naming and history tracking. Use save_to to override with a custom path. Args: - task_id (string): Task ID of completed model (required) - task_type (enum, optional): Task type to route to correct endpoint (default:. It is categorised as a Write tool in the Meshy MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Meshy MCP Server MCP server in PolicyLayer and add a rule for meshy_download_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 Meshy MCP Server. Nothing to install.
meshy_download_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 meshy_download_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 meshy_download_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.
meshy_download_model is provided by the Meshy MCP Server MCP server (meshy-dev/meshy-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Meshy 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.
20 Meshy MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.