generate_3d_model
AI agents invoke generate_3d_model 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.
The description is empty, so confidence is lowered. Based on the name and server context, this tool likely triggers an external 3D model generation process (calling Meshy API or similar), which constitutes executing an external operation. It may also involve writing/publishing content. Execute is chosen as the most appropriate category given it triggers external computational processes.
From the tool's definition Tool name 'generate_3d_model' and server description mentions generating 3D model turntable videos and publishing to BoTTube, implying external API calls and resource consumption.
Attacks that exploit this kind of access
generate_3d_model. 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_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 Bottube. Nothing to install.
generate_3d_model 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_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 generate_3d_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.
generate_3d_model 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 →