get_asset_usage
Code or steps to load an asset in three.js, React Three Fiber, <model-viewer>, Blender, Godot or Unity.
This record as markdown: /tools/3dassets-mcp/get-asset-usage.md
What get_asset_usage does on 3dassets
AI agents call get_asset_usage 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 |
|---|---|---|---|
slug | string | Yes | |
framework | string | — |
Parameters from the server's own tool schema.
Why get_asset_usage is rated Low
Even though get_asset_usage 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 get_asset_usage 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 get_asset_usage, this is the rule to start with:
get_asset_usage 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 get_asset_usage call is checked against it from then on.
Questions about get_asset_usage
Code or steps to load an asset in three.js, React Three Fiber, <model-viewer>, Blender, Godot or Unity. It is categorised as a Read tool in the 3dassets MCP Server, which means it retrieves data without modifying state.
get_asset_usage accepts 2 parameters: slug, framework. Required: slug. 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 get_asset_usage: 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.
get_asset_usage 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 get_asset_usage 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 get_asset_usage. 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.
get_asset_usage 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