Delete a text-to-3D task.
AI agents call text_to_3d_delete to permanently remove resources in Meshy — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The delete operation cannot be undone and results in permanent loss of the 3D model generation task and potentially its output. This is more severe than Write (reversible modification) and meets the Destructive category definition of irreversibly deleting data. While not critical in financial impact, a user could lose significant computational work and generated assets.
From the tool's definition Tool name contains 'delete' and description states 'Delete a text-to-3D task.' This operation irreversibly removes a generated 3D model task and its associated data.
Attacks that exploit this kind of access
Delete a text-to-3D task. It is categorised as a Destructive tool in the Meshy MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Meshy MCP server in PolicyLayer and add a rule for text_to_3d_delete: 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. Nothing to install.
text_to_3d_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the text_to_3d_delete 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 text_to_3d_delete. 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.
text_to_3d_delete is provided by the Meshy MCP server (meshy-mcp-server). 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 →