Get the status of a 3D model generation task. IMPORTANT: This tool checks the status of a task started by create_3d_model_from_text. You may need to call this tool MULTIPLE TIMES until the task completes. Typical workflow: 1. Call this tool with the task_id from create_3d_model_from_text 2. Check...
AI agents call get_task_status to retrieve information from Tripo MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure query/polling operation that checks the state of an existing task. It has no side effects—it only retrieves information about a task that was previously initiated. The tool does not create, modify, delete, or execute anything; it merely returns status data. This is a classic Read operation with minimal risk.
From the tool's definition Tool name is 'get_task_status' and description explicitly states 'Get the status of a 3D model generation task.' It retrieves status information without modifying, deleting, executing, or creating resources.
Documented attack patterns abuse exactly the kind of access get_task_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Tripo MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_task_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_task_status": {}
}
}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.
Get the status of a 3D model generation task. IMPORTANT: This tool checks the status of a task started by create_3d_model_from_text. You may need to call this tool MULTIPLE TIMES until the task completes. Typical workflow: 1. Call this tool with the task_id from create_3d_model_from_text 2. Check the status in the response: - If status is SUCCESS, the task is complete and you can use the pbr_model_url - If status is FAILED, CANCELLED, BANNED, or EXPIRED, the task failed - If status is anything else, the task is still in progress 3. If the task is still in progress, wait a moment and call this tool again Args: task_id: The ID of the task to check (obtained from create_3d_model_from_text). Returns: A dictionary containing the task status and other information. It is categorised as a Read tool in the Tripo MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Tripo MCP Server MCP server in PolicyLayer and add a rule for 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 Tripo MCP Server. Nothing to install.
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 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 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.
get_task_status is provided by the Tripo MCP Server MCP server (vast-ai-research/tripo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 16 Tripo MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
16 Tripo MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.