Apply a previously downloaded Polyhaven texture to an object.
AI agents use set_texture to create or update resources in BlenderMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your BlenderMCP environment.
Texture application modifies scene state (Write category) rather than reading data (Read) or permanently destroying it (Destructive). While Blender's execute_blender_code could produce more severe outcomes, set_texture's scope is limited to cosmetic/material properties.
From the tool's definition Tool applies/modifies textures on objects ('Apply a previously downloaded Polyhaven texture to an object'). This is a modification action that changes object properties but is reversible—textures can be replaced, removed, or reverted without data loss.
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 BlenderMCP, 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. It is categorised as a Write tool in the BlenderMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Blender 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 BlenderMCP. 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 Blender MCP server (nanashi1526/blender-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from BlenderMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
17 BlenderMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.