One-shot: prompt -> Meshy 3D -> turntable -> video -> YouTube upload.
AI agents use meshy_to_youtube to create or update resources in Meshy Youtube — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meshy Youtube environment.
This tool creates new video content and uploads it to YouTube, which is a reversible modification of data/content on a platform. While the upload creates permanent-appearing content, it can be deleted from YouTube afterward, distinguishing it from Destructive actions. The severity is high because unauthorized use could spam a YouTube channel, damage reputation, and consume resources.
From the tool's definition Tool description explicitly states 'YouTube upload', which creates and publishes content to YouTube. The multi-step process (prompt → 3D model → turntable → video → upload) culminates in a Write action that modifies a user's YouTube channel by adding new…
Attacks that exploit this kind of access
One-shot: prompt -> Meshy 3D -> turntable -> video -> YouTube upload. It is categorised as a Write tool in the Meshy Youtube MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Meshy Youtube MCP server in PolicyLayer and add a rule for meshy_to_youtube: 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 Youtube. Nothing to install.
meshy_to_youtube 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 meshy_to_youtube 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 meshy_to_youtube. 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.
meshy_to_youtube is provided by the Meshy Youtube MCP server (scottcjn/meshy-youtube-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 →