Delete a retexture task.
AI agents call retexture_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.
This tool deletes a retexture task, which is an irreversible operation that cannot be undone. Destructive is the most severe applicable category since the action destroys data without recovery possibility. Severity is high because deletion of user-created content (retexture tasks) results in permanent loss, though the blast radius is limited to a single task rather than wholesale database destruction.
From the tool's definition Tool name is 'retexture_delete' and description states 'Delete a retexture task.' The 'delete' operation is irreversible and removes data permanently.
Attacks that exploit this kind of access
Delete a retexture 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 retexture_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.
retexture_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 retexture_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 retexture_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.
retexture_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 →