# gaudio_create_job

Create a processing job with an uploaded file. For Stem Separation models (gsep_music_hq_v1, gsep_music_shq_v1, gsep_speech_hq_v1), the

Agent View of the PolicyLayer registry record for `gaudio_create_job`. HTML page: https://policylayer.com/tools/com-gaudiolab-mcp-developers/gaudio-create-job

## Facts

- Tool: `gaudio_create_job`
- 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_create_job",
    "arguments": {}
  }
}
```

## Why gaudio_create_job is rated Medium

This tool creates a new processing job on the server. It initiates a job resource (a write operation) using a previously uploaded file. While it triggers processing, it is primarily a resource-creation action with reversible/manageable effects (the job can be monitored or cancelled), placing it in Write rather than Execute. No data is deleted, no money is moved, and no arbitrary code is run.

From the tool's own definition: "'Create a processing job with an uploaded file'"

## Use case

AI agents use gaudio_create_job 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_create_job": {
      "limits": [
        {
          "counter": "gaudio_create_job_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_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