Generate a 3D model from 1–4 images using Meshy AI. Use multiple views of the same object for better 3D reconstruction. Image Input (provide ONE of these): - image_urls (array): 1–4 publicly accessible image URLs - file_paths (array): 1–4 absolute paths to LOCAL image files. Server reads and enco...
AI agents use meshy_multi_image_to_3d 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 creates a new 3D model asset by processing input images through AI. It is a generative/write operation that produces new content on the Meshy platform. It is not destructive, financial, or merely reading data. While it triggers an external AI process, the primary outcome is creating a new artifact (Write), not executing arbitrary code or commands.
From the tool's definition Generate a 3D model from 1–4 images using Meshy AI
Documented attack patterns abuse exactly the kind of access meshy_multi_image_to_3d 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_multi_image_to_3d:
{
"version": "1",
"default": "deny",
"tools": {
"meshy_multi_image_to_3d": {
"limits": [
{
"counter": "meshy_multi_image_to_3d_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}meshy_multi_image_to_3d 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.
Generate a 3D model from 1–4 images using Meshy AI. Use multiple views of the same object for better 3D reconstruction. Image Input (provide ONE of these): - image_urls (array): 1–4 publicly accessible image URLs - file_paths (array): 1–4 absolute paths to LOCAL image files. Server reads and encodes them automatically. IMPORTANT: For local files, always use file_paths instead of manually base64-encoding. Other Args: - ai_model:. 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_multi_image_to_3d: 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_multi_image_to_3d 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_multi_image_to_3d 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_multi_image_to_3d. 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_multi_image_to_3d 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.