One-shot: an image -> Meshy image-to-3D -> turntable -> BoTTube video.
AI agents invoke image_to_bottube 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 chains multiple external operations: it triggers a 3D model generation via Meshy (external API call), renders a turntable video, and publishes it to BoTTube (external platform). This constitutes executing a multi-step external pipeline with side effects including resource consumption, 3D model creation, and public/external video publication.
From the tool's definition One-shot: an image -> Meshy image-to-3D -> turntable -> BoTTube video
Attacks that exploit this kind of access
One-shot: an image -> Meshy image-to-3D -> turntable -> BoTTube video. 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 image_to_bottube: 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.
image_to_bottube 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 image_to_bottube 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_bottube. 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_bottube 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 →