AI agents call delete_retexture_task to permanently remove resources in Meshy AI MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion operations are irreversible and cannot be undone. Once a retexture task is deleted, it cannot be recovered. This meets the definition of Destructive category. Severity is high because an agent could delete tasks without authorization or by mistake, causing loss of work and user data. Confidence is high because the name and description explicitly use 'delete' language with no ambiguity.
From the tool's definition Tool name is 'delete_retexture_task' and description states 'Delete a retexture task.' The verb 'delete' indicates irreversible removal of data (a retexture task record).
Documented attack patterns abuse exactly the kind of access delete_retexture_task gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Meshy AI MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_retexture_task:
{
"version": "1",
"default": "deny",
"hide": [
"delete_retexture_task"
]
}delete_retexture_task disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a retexture task. It is categorised as a Destructive tool in the Meshy AI MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Meshy AI MCP Server MCP server in PolicyLayer and add a rule for delete_retexture_task: 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 AI MCP Server. Nothing to install.
delete_retexture_task 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 delete_retexture_task 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 delete_retexture_task. 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.
delete_retexture_task is provided by the Meshy AI MCP Server MCP server (pasie15/meshy-ai-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 51 Meshy AI MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
51 Meshy AI MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.