tripo3d_get_task_status
AI agents call tripo3d_get_task_status to retrieve information from Tripo3D MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to query the status of asynchronous 3D generation tasks (given sibling tools like tripo3d_text_to_model and tripo3d_image_to_model which likely return task IDs). Status queries are read-only operations with no side effects. Confidence is slightly lowered due to empty description, but the function name is sufficiently clear that this is a safe information retrieval tool.
From the tool's definition Tool name 'tripo3d_get_task_status' indicates status retrieval; no description provided, but the naming pattern suggests a query operation that retrieves existing task status information without modifying or executing operations.
Attacks that exploit this kind of access
tripo3d_get_task_status. It is categorised as a Read tool in the Tripo3D MCP MCP Server, which means it retrieves data without modifying state.
Register the Tripo3D MCP server in PolicyLayer and add a rule for tripo3d_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 Tripo3D MCP. Nothing to install.
tripo3d_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 tripo3d_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 tripo3d_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.
tripo3d_get_task_status is provided by the Tripo3D MCP server (lxy2109/tripo-mcp). 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 →