Check task status or wait for completion. Supports two modes: wait=true (default): Auto-polls with exponential backoff (5s→30s, 15s at 95%+) until SUCCEEDED/FAILED/TIMEOUT. Returns full result with progress bar. Recommended — call once and get the final result. wait=false: Returns current status ...
AI agents call meshy_get_task_status to retrieve information from Meshy MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
meshy_get_task_status is a pure read operation that queries the status of an existing task. It supports polling modes (blocking or non-blocking) but performs no mutations, executions, or destructive actions. The worst case for misuse is retrieving status information about tasks, which poses minimal security risk. This is a standard status-check utility tool.
From the tool's definition The tool description explicitly states it 'Check[s] task status' and 'Returns current status immediately' or 'Returns full result'.
Documented attack patterns abuse exactly the kind of access meshy_get_task_status 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_get_task_status:
{
"version": "1",
"default": "deny",
"tools": {
"meshy_get_task_status": {}
}
} meshy_get_task_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check task status or wait for completion. Supports two modes: wait=true (default): Auto-polls with exponential backoff (5s→30s, 15s at 95%+) until SUCCEEDED/FAILED/TIMEOUT. Returns full result with progress bar. Recommended — call once and get the final result. wait=false: Returns current status immediately (single query) with progress bar. Args: - task_id (string): Task ID returned from generation tools (required) - task_type (enum, optional): Task type for endpoint routing (default:. It is categorised as a Read tool in the Meshy MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Meshy MCP Server MCP server in PolicyLayer and add a rule for meshy_get_task_status: 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_get_task_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the meshy_get_task_status 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_get_task_status. 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_get_task_status 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.