submit_asset_from_url
Submit a .glb hosted at a public https URL on the user’s behalf (requires their API key). We download it, validate and re-encode it, then a human reviews it before publishing. CC0 is automatic, but the user must accept its irrevocable dedication before submission. Max 25 MB, 1M triangles, embedde...
This record as markdown: /tools/3dassets-mcp/submit-asset-from-url.md
What submit_asset_from_url does on 3dassets
AI agents use submit_asset_from_url to create or update resources in 3dassets, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 3dassets environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | |
tags | array | — | |
title | string | Yes | |
aiModel | string | — | Contributor-reported model ID or custom model/tool name; use list_ai_models for suggestions. Omit if unknown. |
license | string | — | Fixed CC0 1.0 Universal dedication; no licence selection |
summary | string | Yes | Plain 1–2 sentence description |
category | string | Yes | From list_categories |
sourceUrl | string | — | Where the original was first published |
aiGenerated | boolean | — | AI helped create geometry, code or textures; not merely uploading |
attestation | boolean | Yes | Required contributor acceptance (including for agent submissions): I confirm that I created this asset or hold the rights to publish it under CC0 1.0 Universal, |
description | string | — | Markdown: scale, pivot, what is included |
Parameters from the server's own tool schema.
Why submit_asset_from_url is rated Medium
An AI agent can call submit_asset_from_url faster than any human can review: one bad instruction and it creates or modifies resources in 3dassets by the hundred, each call as confident as the last.
Risk signalsAccepts URL/endpoint input (url) · High parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs submit_asset_from_url 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 submit_asset_from_url, this is the rule to start with:
submit_asset_from_url stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 submit_asset_from_url call is checked against it from then on.
Questions about submit_asset_from_url
Submit a .glb hosted at a public https URL on the user’s behalf (requires their API key). We download it, validate and re-encode it, then a human reviews it before publishing. CC0 is automatic, but the user must accept its irrevocable dedication before submission. Max 25 MB, 1M triangles, embedded textures only. It is categorised as a Write tool in the 3dassets MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
submit_asset_from_url accepts 11 parameters: url, tags, title, aiModel, license, summary, category, sourceUrl, aiGenerated, attestation, description. Required: url, title, summary, category, attestation. 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 submit_asset_from_url: 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.
submit_asset_from_url 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 submit_asset_from_url 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 submit_asset_from_url. 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.
submit_asset_from_url 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