Render a GLB model as a 360° turntable to PNG frames (requires Blender).
AI agents invoke render_turntable 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 executes an external application (Blender) to process a 3D model file and produce output frames. It involves running a compute-intensive external process whose effects depend on the input arguments. No financial, destructive, or persistent write operations are indicated, but it does execute an external program and produce output files.
From the tool's definition 'Render a GLB model as a 360° turntable to PNG frames (requires Blender)' — triggers execution of Blender to render frames
Attacks that exploit this kind of access
Render a GLB model as a 360° turntable to PNG frames (requires Blender). 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 render_turntable: 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.
render_turntable 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 render_turntable 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 render_turntable. 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.
render_turntable 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 →