check_subtitle_delivery
utilpeek: Check subtitle delivery timing, line length and reading speed. Returns a cue-level SRT/WebVTT delivery review with versioned language/audience profiles: en-US-adult-v1, en-US-children-v1, ja-adult-v1 and ar-adult-v1. Checks overlaps, minimum gaps, duration, line length, line count and c...
This record as markdown: /tools/dev-tanod-tanod/check-subtitle-delivery.md
What check_subtitle_delivery does on Tanod
AI agents call check_subtitle_delivery to retrieve information from Tanod without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
content | string | Yes | SRT or WebVTT text, at most 1,000,000 characters and 10,000 cues. Preserved verbatim in original_content. |
profile | string | Yes | Versioned language/audience rules: English profiles derive from Netflix guides; Japanese/Arabic are Tanod heuristics, not platform approval. Full timing, line/C |
from_format | object | — | Optional input format; otherwise detect WEBVTT header. |
intentional_overlaps | array | — | Unique 1-based cue numbers in file order: downgrade only their overlap finding to a warning, e.g. concurrent speakers. No cue is modified; other checks still ap |
Parameters from the server's own tool schema.
Why check_subtitle_delivery is rated Low
Even though check_subtitle_delivery only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsAccepts raw HTML/template content (content)
Attacks that exploit this kind of access
The rule that runs check_subtitle_delivery safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tanod, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_subtitle_delivery, this is the rule to start with:
check_subtitle_delivery is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tanod, apply this rule, and every check_subtitle_delivery call is checked against it from then on.
Questions about check_subtitle_delivery
utilpeek: Check subtitle delivery timing, line length and reading speed. Returns a cue-level SRT/WebVTT delivery review with versioned language/audience profiles: en-US-adult-v1, en-US-children-v1, ja-adult-v1 and ar-adult-v1. Checks overlaps, minimum gaps, duration, line length, line count and characters per second (Unicode grapheme clusters, not bytes or display columns). At most 1,000,000 characters and 10,000 cues. Findings and suggestions are separate from the original file and cues. No platform approval. English profiles are based on official Netflix guides read 2026-10-22; Japanese/Arabic profiles are Tanod heuristics. Counting and the 80 ms gap are Tanod choices. No audio alignment or missing-speech detection. First 1,000 finding details, exact totals. Malformed input is a 422, not charged. Typically under 0.3 s. Price: USD 0.002. Free: 10 utilpeek calls per IP per UTC day. It is categorised as a Read tool in the Tanod MCP Server, which means it retrieves data without modifying state.
check_subtitle_delivery accepts 4 parameters: content, profile, from_format, intentional_overlaps. Required: content, profile. The full parameter table on this page comes from the server's own tool schema.
Register the Tanod MCP server in PolicyLayer and add a rule for check_subtitle_delivery: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Tanod. Nothing to install.
check_subtitle_delivery is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the check_subtitle_delivery rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for check_subtitle_delivery. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
check_subtitle_delivery is provided by the Tanod MCP server (https://tanod.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tanod, and thousands of servers like it.
This server
Across the catalogue