# gaudio_get_job

Check job status and get results. Status:

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

## Facts

- Tool: `gaudio_get_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: Read (Low risk)
- Registry record: grade B, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

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

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

## Why gaudio_get_job is rated Low

This tool retrieves information about existing jobs and their results. It performs a query operation to check status and fetch results, which is characteristic of a Read category tool. There is no data creation, modification, deletion, code execution, or financial operation involved. The blast radius is minimal as it only exposes data that has already been processed.

From the tool's own definition: "Tool name 'gaudio_get_job' and description 'Check job status and get results' indicates retrieval of job status and output data without modification or side effects."

## Use case

AI agents call gaudio_get_job to retrieve information from Mcp Developers without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "gaudio_get_job": {}
  }
}
```

## Other tools on Mcp Developers (6)

- `gaudio_separate_audio` — Execute — https://policylayer.com/tools/com-gaudiolab-mcp-developers/gaudio-separate-audio.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