wait_for_task · Meshy MCP: Risk & Policy

WHAT IT DOES

What wait_for_task does on Meshy

AI agents invoke wait_for_task to trigger actions in Meshy. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why wait_for_task needs a policy

This tool executes an external operation (task polling against Meshy.ai API) and waits for completion. While it doesn't directly create, delete, or modify data like sibling tools (animation_create, image_to_3d_create), it actively orchestrates and retrieves results from asynchronous operations. The polling mechanism and dependency on task arguments classify it as Execute rather than Read.

From the tool's definition Tool 'wait_for_task' polls a task until terminal state and returns results with download URLs. It triggers external API operations (waiting/polling) whose effects depend on which task is being polled.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wait_for_task Rate-limited

wait_for_task stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wait_for_task": {
      "limits": [
        {
          "counter": "wait_for_task_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Meshy, so you can run agents against it safely.

FAQ

Questions about wait_for_task

What does the wait_for_task tool do? +

Poll a task until it reaches a terminal state (SUCCEEDED, FAILED, or CANCELED). Returns the final task result with download URLs. Use this instead of manually calling _get in a loop. It is categorised as a Execute tool in the Meshy MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on wait_for_task? +

Register the Meshy MCP server in PolicyLayer and add a rule for wait_for_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. Nothing to install.

What risk level is wait_for_task? +

wait_for_task is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit wait_for_task? +

Yes. Add a rate_limit block to the wait_for_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.

How do I block wait_for_task completely? +

Set action: deny in the PolicyLayer policy for wait_for_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.

What MCP server provides wait_for_task? +

wait_for_task 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.