# gaudio_separate_audio

All-in-one audio separation: upload file (or reuse uploadId) → create job → poll until done → return download URLs. For Stem Separation, provide

Agent View of the PolicyLayer registry record for `gaudio_separate_audio`. HTML page: https://policylayer.com/tools/com-gaudiolab-mcp-developers/gaudio-separate-audio

## Facts

- Tool: `gaudio_separate_audio`
- 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: Execute (High 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_separate_audio",
    "arguments": {}
  }
}
```

## Why gaudio_separate_audio is rated High

This tool orchestrates a multi-step pipeline: uploading a file, creating a processing job, polling for completion, and returning results. It triggers an external audio AI processing operation whose effects depend on the input arguments (file and model parameters). This is an Execute-category action as it runs an external operation/workflow, not merely reading data or writing a simple record.

From the tool's own definition: "upload file (or reuse uploadId) → create job → poll until done → return download URLs"

## Use case

AI agents invoke gaudio_separate_audio to trigger actions in Mcp Developers. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

## 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_separate_audio": {
      "limits": [
        {
          "counter": "gaudio_separate_audio_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Mcp Developers (6)

- `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
- `gaudio_upload_file` — Write — https://policylayer.com/tools/com-gaudiolab-mcp-developers/gaudio-upload-file.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