# delete_job

Permanently delete a finished (done or errored) transcription job and its stored text. Refused while the job is queued or running. This cannot be undone.

Agent View of the PolicyLayer registry record for `delete_job`. HTML page: https://policylayer.com/tools/com-fieldtranscript-transcriber/delete-job

## Facts

- Tool: `delete_job`
- Server: FieldTranscript (`https://mcp.fieldtranscript.com/mcp`) — https://policylayer.com/tools/com-fieldtranscript-transcriber.md
- Homepage: https://github.com/https://mcp.fieldtranscript.com/mcp
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Hidden

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `job_id` | string | yes |  |

Parameters from the server's own tool schema.

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "delete_job",
    "arguments": {
      "job_id": "<job_id>"
    }
  }
}
```

## Why delete_job is rated Critical

An AI agent that decides to call delete_job doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from FieldTranscript is gone. There is no undo for destructive operations.

## Use case

AI agents call delete_job to permanently remove resources in FieldTranscript, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_job"
  ]
}
```

## Other tools on FieldTranscript (3)

- `get_job` — Read — https://policylayer.com/tools/com-fieldtranscript-transcriber/get-job.md
- `list_jobs` — Read — https://policylayer.com/tools/com-fieldtranscript-transcriber/list-jobs.md
- `submit_transcription` — Write — https://policylayer.com/tools/com-fieldtranscript-transcriber/submit-transcription.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-fieldtranscript-transcriber · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-fieldtranscript-transcriber