download_polyhaven_asset
AI agents use download_polyhaven_asset 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.
A download operation fetches external data and writes it to the local filesystem or Blender scene, making Write the most appropriate category. However, the description is empty, so confidence is reduced. It could also be Execute if it triggers further processing. Given the sibling tools context (Blender asset management), downloading an asset likely imports/writes it into the scene.
From the tool's definition Tool name 'download_polyhaven_asset' and empty description. Based on name alone, it downloads assets from Polyhaven into Blender.
Attacks that exploit this kind of access
download_polyhaven_asset. 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 download_polyhaven_asset: 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.
download_polyhaven_asset 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 download_polyhaven_asset 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 download_polyhaven_asset. 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.
download_polyhaven_asset is provided by the Blender MCP server (opslon/blender-mcp-optimized). 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 →