One-shot: re-texture an existing model -> turntable -> BoTTube video.
AI agents use retexture_to_bottube to create or update resources in Meshy Bottube — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meshy Bottube environment.
This tool modifies data (re-texturing a model) reversibly and publishes it to an external platform (BoTTube). Re-texturing is not destructive since the original model remains and the operation can be undone or overwritten. It does not execute arbitrary code, delete data, or move money. The publishing action creates new content rather than executing system commands.
From the tool's definition Tool description states 're-texture an existing model -> turntable -> BoTTube video', indicating it modifies an existing 3D model (re-texturing) and publishes the result.
Attacks that exploit this kind of access
One-shot: re-texture an existing model -> turntable -> BoTTube video. It is categorised as a Write tool in the Meshy Bottube MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Meshy Bottube MCP server in PolicyLayer and add a rule for retexture_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.
retexture_to_bottube 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 retexture_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 retexture_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.
retexture_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 →