# gaudio_upload_file

Upload a local audio/video/text file to Gaudio servers. Handles multipart upload automatically (create → chunk upload → complete). The returned uploadId is valid for 72 hours and can be reused across multiple jobs. Supported formats: WAV, FLAC, MP3, M4A, MOV, MP4, TXT.

Agent View of the PolicyLayer registry record for `gaudio_upload_file`. HTML page: https://policylayer.com/tools/com-gaudiolab-mcp-developers/gaudio-upload-file

## Facts

- Tool: `gaudio_upload_file`
- Server: Mcp Developers (`@gaudiolab/mcp-developers`) — https://policylayer.com/tools/com-gaudiolab-mcp-developers.md
- Install: `npx -y @gaudiolab/mcp-developers`
- Homepage: https://www.npmjs.com/package/@gaudiolab/mcp-developers
- Risk category: Write (Medium risk)
- Registry record: grade B, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "gaudio_upload_file",
    "arguments": {}
  }
}
```

## Why gaudio_upload_file is rated Medium

This tool creates and stores data on remote servers in a reversible manner (uploaded files can be deleted or replaced). It does not execute code, delete data irreversibly, or move money. The medium severity reflects that malicious file uploads (e.g., large files, spam content, or files used in subsequent processing) could waste resources or feed into downstream AI operations, but the action itself is reversible.

From the tool's own definition: "Tool description states 'Upload a local audio/video/text file to Gaudio servers' and 'create → chunk upload → complete', indicating file creation/storage on remote servers."

## Use case

AI agents use gaudio_upload_file to create or update resources in Mcp Developers, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Developers environment.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mcp Developers:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "gaudio_upload_file": {
      "limits": [
        {
          "counter": "gaudio_upload_file_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Mcp Developers (6)

- `gaudio_separate_audio` — Execute — https://policylayer.com/tools/com-gaudiolab-mcp-developers/gaudio-separate-audio.md
- `gaudio_get_job` — Read — https://policylayer.com/tools/com-gaudiolab-mcp-developers/gaudio-get-job.md
- `gaudio_get_key_info` — Read — https://policylayer.com/tools/com-gaudiolab-mcp-developers/gaudio-get-key-info.md
- `gaudio_list_models` — Read — https://policylayer.com/tools/com-gaudiolab-mcp-developers/gaudio-list-models.md
- `gaudio_create_job` — Write — https://policylayer.com/tools/com-gaudiolab-mcp-developers/gaudio-create-job.md
- `gaudio_sync_lyrics` — Write — https://policylayer.com/tools/com-gaudiolab-mcp-developers/gaudio-sync-lyrics.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-gaudiolab-mcp-developers · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-gaudiolab-mcp-developers