# submit_transcription

Submit a public video or audio URL (YouTube etc.) for verbatim transcription. Returns a job_id immediately. Transcription takes ~1-10 minutes: poll get_job with the job_id every 30-60 seconds until status is 'done', then call get_job with include_transcript=true. Not for private/internal URLs.

Agent View of the PolicyLayer registry record for `submit_transcription`. HTML page: https://policylayer.com/tools/com-fieldtranscript-transcriber/submit-transcription

## Facts

- Tool: `submit_transcription`
- 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: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `url` | 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": "submit_transcription",
    "arguments": {
      "url": "<url>"
    }
  }
}
```

## Why submit_transcription is rated Medium

An AI agent can call submit_transcription faster than any human can review: one bad instruction and it creates or modifies resources in FieldTranscript by the hundred, each call as confident as the last.

Risk signals: Accepts URL/endpoint input (url) · Bulk/mass operation — affects multiple targets

## Use case

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

## Recommended policy (PolicyLayer)

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

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

## Other tools on FieldTranscript (3)

- `delete_job` — Destructive — https://policylayer.com/tools/com-fieldtranscript-transcriber/delete-job.md
- `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

## 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