Delete an image-to-image task.
AI agents call image_to_image_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 permanently removes an image-to-image generation task, which cannot be undone. Deletion operations are irreversible and fall into the Destructive category. The severity is high because an AI agent could inadvertently delete important user-generated tasks or results, causing data loss. The confidence is high due to the explicit 'delete' terminology in both the tool name and description.
From the tool's definition The tool name is 'image_to_image_delete' and the description states 'Delete an image-to-image task.' The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete an image-to-image 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 image_to_image_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.
image_to_image_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 image_to_image_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 image_to_image_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.
image_to_image_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 →