search_assets
Search the free GLB catalogue on 3dassets.dev (three.js, Blender, Godot, Unity) by text, category (what it is), theme (what world) and style (what look). Returns direct CDN URLs (CORS *, immutable) that load with a plain GLTFLoader. Published models use CC0 1.0 Universal: free personal and commer...
This record as markdown: /tools/3dassets-mcp/search-assets.md
What search_assets does on 3dassets
AI agents call search_assets to retrieve information from 3dassets without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
q | string | — | Alias for query, as spelled by the REST API |
tag | string | — | Any tag slug from list_tags |
page | integer | — | |
sort | string | — | Default: best match for a query, newest otherwise |
limit | integer | — | |
query | string | — | Free-text search over title and summary |
style | string | — | Style tag slug, e.g. low-poly, realistic, voxel |
theme | string | — | Theme tag slug, e.g. sci-fi, fantasy, modern |
category | string | — | Category slug from list_categories |
Parameters from the server's own tool schema.
Why search_assets is rated Low
Even though search_assets only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs search_assets safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 3dassets, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_assets, this is the rule to start with:
search_assets is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 3dassets, apply this rule, and every search_assets call is checked against it from then on.
Questions about search_assets
Search the free GLB catalogue on 3dassets.dev (three.js, Blender, Godot, Unity) by text, category (what it is), theme (what world) and style (what look). Returns direct CDN URLs (CORS *, immutable) that load with a plain GLTFLoader. Published models use CC0 1.0 Universal: free personal and commercial use without attribution. Licence metadata is retained in each result. It is categorised as a Read tool in the 3dassets MCP Server, which means it retrieves data without modifying state.
search_assets accepts 9 parameters: q, tag, page, sort, limit, query, style, theme, category. The full parameter table on this page comes from the server's own tool schema.
Register the 3dassets MCP server in PolicyLayer and add a rule for search_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 3dassets. Nothing to install.
search_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_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_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_assets is provided by the 3dassets MCP server (3dassets-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 3dassets, and thousands of servers like it.
This server
Across the catalogue