search_polyhaven_assets
AI agents call search_polyhaven_assets to retrieve information from BlenderMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a search operation against a public 3D asset library. It retrieves information about available assets without modifying data, executing code, or causing irreversible changes. The blast radius is minimal—worst case, an AI agent wastes API calls or downloads unwanted assets, but no data is destroyed and no code executes server-side. Classified as Read with low severity.
From the tool's definition Tool name 'search_polyhaven_assets' indicates querying/searching asset library; 'search' typically retrieves data without side effects. Server context shows asset library integration (PolyHaven is a free 3D asset repository).
Attacks that exploit this kind of access
search_polyhaven_assets. It is categorised as a Read tool in the BlenderMCP MCP Server, which means it retrieves data without modifying state.
Register the Blender MCP server in PolicyLayer and add a rule for search_polyhaven_assets: 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.
search_polyhaven_assets 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 search_polyhaven_assets 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 search_polyhaven_assets. 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.
search_polyhaven_assets 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 →