Apply a previously downloaded Polyhaven texture to an object. Parameters: - object_name: Name of the object to apply the texture to - texture_id: ID of the Polyhaven texture to apply (must be downloaded first) Returns a message indicating success or failure.
AI agents use set_texture to create or update resources in Tripo MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tripo MCP Server environment.
This tool modifies existing 3D objects by applying textures to them. This is a Write operation because it creates or modifies data reversibly—textures can be removed or changed without permanently destroying the object or its geometry. While it affects the 3D scene state, it is not Destructive (the object remains intact), Execute (it does not run arbitrary code or external commands), or Financial.
From the tool's definition Tool applies a texture to an object, which modifies the visual properties and state of a 3D scene asset. The description states 'Apply a previously downloaded Polyhaven texture to an object,' indicating a reversible modification of object attributes.
Documented attack patterns abuse exactly the kind of access set_texture 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 set_texture:
{
"version": "1",
"default": "deny",
"tools": {
"set_texture": {
"limits": [
{
"counter": "set_texture_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_texture stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Apply a previously downloaded Polyhaven texture to an object. Parameters: - object_name: Name of the object to apply the texture to - texture_id: ID of the Polyhaven texture to apply (must be downloaded first) Returns a message indicating success or failure. It is categorised as a Write tool in the Tripo MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tripo MCP Server MCP server in PolicyLayer and add a rule for set_texture: 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.
set_texture is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_texture 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 set_texture. 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.
set_texture 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.