Delete a remesh task.
AI agents call remesh_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.
Deletion operations that remove user-generated content or computational tasks are destructive by definition. Users lose access to their remesh task and any associated data. While the severity is not 'critical' (no direct financial loss or security breach), it is 'high' because the action is irreversible and impacts user assets (generated 3D models/tasks).
From the tool's definition Tool name explicitly states 'delete' and description confirms 'Delete a remesh task' — this irreversibly removes a generated 3D model remesh task from the Meshy.ai service. The action cannot be undone.
Attacks that exploit this kind of access
Delete a remesh 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 remesh_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.
remesh_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 remesh_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 remesh_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.
remesh_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 →