AI agents call delete_remesh_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.
This tool irreversibly deletes a remesh task, which cannot be undone. Deletion of user-created assets (remesh tasks) represents destructive action. Severity is 'high' rather than 'critical' because the blast radius is limited to a single task rather than bulk operations or system-wide data, but the impact is still significant as tasks represent valuable AI-generated work product that could be in progress or…
From the tool's definition Tool name 'delete_remesh_task' explicitly performs a delete operation. Description states 'Delete a remesh task,' confirming irreversible removal of data.
Documented attack patterns abuse exactly the kind of access delete_remesh_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_remesh_task:
{
"version": "1",
"default": "deny",
"hide": [
"delete_remesh_task"
]
}delete_remesh_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 remesh 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_remesh_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_remesh_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_remesh_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_remesh_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_remesh_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.