Get the current status and result of any Tripo task. Poll this after creating a task to check progress and retrieve the output model URLs.
AI agents call get_task_status to retrieve information from Tripo AI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the status of existing tasks and retrieves results. It performs information retrieval without modifying, executing, or deleting any data. The blast radius of misuse is minimal—an attacker could only view task statuses and model URLs they may already have access to, posing no destructive or financial risk.
From the tool's definition Tool description explicitly states 'Get the current status and result' and 'Poll this after creating a task to check progress and retrieve the output model URLs.' The verb 'Get' and 'retrieve' indicate read-only data retrieval with no side effects.
Attacks that exploit this kind of access
Get the current status and result of any Tripo task. Poll this after creating a task to check progress and retrieve the output model URLs. It is categorised as a Read tool in the Tripo AI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Tripo AI 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 AI 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 AI MCP Server MCP server (pasie15/tripo-ai-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 →