Image-to-3D: a photo/render (public URL or local file path) -> textured
AI agents invoke generate_3d_from_image to trigger actions in Meshy Bottube. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an external 3D model generation operation from an image input, which involves running a remote AI processing pipeline. It is not a simple read or write — it executes a generation task on an external service (Meshy). The blast radius is medium since it consumes API credits and initiates external compute, but does not directly delete data or move money.
From the tool's definition Image-to-3D: a photo/render (public URL or local file path) -> textured
Attacks that exploit this kind of access
Image-to-3D: a photo/render (public URL or local file path) -> textured. It is categorised as a Execute tool in the Meshy Bottube MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Meshy Bottube MCP server in PolicyLayer and add a rule for generate_3d_from_image: 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 Bottube. Nothing to install.
generate_3d_from_image is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the generate_3d_from_image 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 generate_3d_from_image. 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.
generate_3d_from_image is provided by the Meshy Bottube MCP server (scottcjn/meshy-bottube-mcp). 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 →