New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_upload_url

For clients that can upload bytes: returns a presigned PUT URL for a .glb (and optionally a PNG preview). Then call finalize_upload with the returned keys.

SERVER3dassets SOURCE3dassets-mcp
Low RISK CLASS
Category Read
Parameters 32 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/3dassets-mcp/get-upload-url.md

What get_upload_url does on 3dassets

AI agents call get_upload_url 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.

ParameterTypeRequiredDescription
filename string Yes
withPreview boolean —
contentLength integer Yes

Parameters from the server's own tool schema.

Why get_upload_url is rated Low

Even though get_upload_url 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.

Risk signalsAccepts file system path (filename)

Questions about get_upload_url

What does the get_upload_url tool do? +

For clients that can upload bytes: returns a presigned PUT URL for a .glb (and optionally a PNG preview). Then call finalize_upload with the returned keys. It is categorised as a Read tool in the 3dassets MCP Server, which means it retrieves data without modifying state.

What parameters does get_upload_url accept? +

get_upload_url accepts 3 parameters: filename, withPreview, contentLength. Required: filename, contentLength. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_upload_url? +

Register the 3dassets MCP server in PolicyLayer and add a rule for get_upload_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.

What risk level is get_upload_url? +

get_upload_url is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_upload_url? +

Yes. Add a rate_limit block to the get_upload_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.

How do I block get_upload_url completely? +

Set action: deny in the PolicyLayer policy for get_upload_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.

What MCP server provides get_upload_url? +

get_upload_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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of 3dassets's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.