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.
Search operations are inherently read-only with no side effects—they retrieve data about available 3D assets from Poly Haven but do not create, execute, delete, or modify any data. The tool name clearly indicates a query/search pattern. Although the description is empty, the naming convention and context from sibling tools provide sufficient evidence for low-severity read classification.
From the tool's definition Tool name 'search_polyhaven_assets' indicates a search operation on the Poly Haven asset library. The sibling tools include 'download_polyhaven_asset' and 'get_polyhaven_categories', which are clearly read operations, suggesting this tool queries/lists…
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 (wenyen-hsu/blender-mcp). 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 →