AI agents use image_to_3d_create to create or update resources in Meshy — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meshy environment.
This tool creates a new 3D model resource by processing an input image. It is a creation/write operation that generates a new asset on the Meshy.ai platform. It does not delete or irreversibly destroy data, execute arbitrary code, or move money, making Write the most appropriate category. Severity is medium as misuse could generate unwanted assets or consume API credits.
From the tool's definition Generate a 3D model from a single image
Attacks that exploit this kind of access
Generate a 3D model from a single image. The image_url must be publicly accessible or a base64 data URI. It is categorised as a Write tool in the Meshy MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Meshy MCP server in PolicyLayer and add a rule for image_to_3d_create: 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. Nothing to install.
image_to_3d_create 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 image_to_3d_create 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 image_to_3d_create. 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.
image_to_3d_create is provided by the Meshy MCP server (meshy-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →