Cancel a pending or in-progress 3D generation task. This tool cancels a task that is currently PENDING or IN_PROGRESS. Completed or failed tasks cannot be canceled. Args: - task_id (string): Task ID to cancel (required) - task_type (enum, optional): Task type to route to correct endpoint (default:
AI agents call meshy_cancel_task to permanently remove resources in Meshy MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling a running task is irreversible — the in-progress generation work is terminated and cannot be resumed. This is a destructive operation that permanently stops and discards the task's progress, even though no stored data is deleted.
From the tool's definition Cancel a pending or in-progress 3D generation task... cancels a task that is currently PENDING or IN_PROGRESS
Documented attack patterns abuse exactly the kind of access meshy_cancel_task gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Meshy MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for meshy_cancel_task:
{
"version": "1",
"default": "deny",
"hide": [
"meshy_cancel_task"
]
} meshy_cancel_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.
Cancel a pending or in-progress 3D generation task. This tool cancels a task that is currently PENDING or IN_PROGRESS. Completed or failed tasks cannot be canceled. Args: - task_id (string): Task ID to cancel (required) - task_type (enum, optional): Task type to route to correct endpoint (default:. It is categorised as a Destructive tool in the Meshy MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Meshy MCP Server MCP server in PolicyLayer and add a rule for meshy_cancel_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 MCP Server. Nothing to install.
meshy_cancel_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 meshy_cancel_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 meshy_cancel_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.
meshy_cancel_task is provided by the Meshy MCP Server MCP server (meshy-dev/meshy-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Meshy MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
20 Meshy MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.