AI agents use upload_glb to create or update resources in Portals — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Portals environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
filePath | string | — | Absolute path to a .glb file. Required unless folderPath is provided. |
folderPath | string | — | Absolute path to a folder containing .glb files. When provided (and filePath is not), uploads all .glb files in the folder. |
enableDraco | boolean | — | Enable Draco compression (default: false) |
Parameters from the server's own tool schema.
Uploading files to a CDN is a write operation—it creates or modifies data in persistent storage. It is not Destructive because uploads are reversible (assets can be deleted later). It is not Execute because it doesn't run arbitrary code or commands; it simply transfers files.
From the tool's definition Tool description states it "Upload[s] a .glb file (or all .glb files from a folder) to the Portals CDN" and "Returns the asset URL(s)". This is a reversible create/modify operation that adds new assets to cloud storage without irreversible deletion.
Risk signalsAccepts file system path (filePath)
Attacks that exploit this kind of access
Upload a .glb file (or all .glb files from a folder) to the Portals CDN. Provide filePath for a single file, or folderPath to upload all .glb files in a directory. Returns the asset URL(s). It is categorised as a Write tool in the Portals MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
upload_glb accepts 3 parameters: filePath, folderPath, enableDraco. The full parameter table on this page comes from the server's own tool schema.
Register the Portals MCP server in PolicyLayer and add a rule for upload_glb: 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 Portals. Nothing to install.
upload_glb 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 upload_glb 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 upload_glb. 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.
upload_glb is provided by the Portals MCP server (portals-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 →