Import a GLB model from URL into Blender scene Parameters: - glb_url: Download URL of the GLB model file Returns: Result message of the import operation
AI agents invoke import_tripo_glb_model to trigger actions in Tripo MCP Server. 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.
This tool fetches a file from an external URL and imports it into an active Blender scene, which constitutes an external operation with side effects on the Blender environment. It's not purely Read (it modifies the scene state) and not Write in the traditional sense (it executes an import operation that depends on external URL arguments).
From the tool's definition Import a GLB model from URL into Blender scene — triggers an external operation (downloading from a URL and importing into Blender scene)
Documented attack patterns abuse exactly the kind of access import_tripo_glb_model 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 import_tripo_glb_model:
{
"version": "1",
"default": "deny",
"tools": {
"import_tripo_glb_model": {
"limits": [
{
"counter": "import_tripo_glb_model_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} import_tripo_glb_model 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.
Free to start. No card required.
Import a GLB model from URL into Blender scene Parameters: - glb_url: Download URL of the GLB model file Returns: Result message of the import operation. It is categorised as a Execute tool in the Tripo MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Tripo MCP Server MCP server in PolicyLayer and add a rule for import_tripo_glb_model: 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.
import_tripo_glb_model is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the import_tripo_glb_model 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 import_tripo_glb_model. 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.
import_tripo_glb_model 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.