Asynchronously analyse a video with Pegasus 1.5 (default). Takes a videoUrl, assetId, or base64Video directly — NO prior indexing required. Handles videos up to 2 hours; longer videos are rejected by the Twelve Labs API with a 400. Pegasus 1.5 supports both prompt-only general analysis and time_b...
Risk signalsAccepts URL/endpoint input (promptV2.mediaSources[].url) · High parameter count (37 properties) · Bulk/mass operation — affects multiple targets
Part of the Twelvelabs Mcp Server server.
Free to start. No card required.
AI agents call async-analyse-video to retrieve information from Twelvelabs Mcp Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though async-analyse-video only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"async-analyse-video": {}
}
}See the full Twelvelabs Mcp Server policy for all 24 tools.
These attack patterns abuse exactly the kind of access async-analyse-video gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Asynchronously analyse a video with Pegasus 1.5 (default). Takes a videoUrl, assetId, or base64Video directly — NO prior indexing required. Handles videos up to 2 hours; longer videos are rejected by the Twelve Labs API with a 400. Pegasus 1.5 supports both prompt-only general analysis and time_based_metadata segmentation; pick the mode by setting analysisMode and segmentDefinitions (segmentation) or just prompt (general). Pegasus 1.2 is retained for backwards compatibility — set modelName="pegasus1.2" only if you need to preserve an existing 1.2 workflow (1.2 is on a deprecation path). This is the right tool when: - You have a URL or local upload, not an indexed videoId. - The video is over 1 hour long (sync analyse is capped at 1h). - You want time-based metadata segmentation (set analysisMode="time_based_metadata" + segmentDefinitions; Pegasus 1.5 only). - You want multimodal prompting: attach up to 4 reference images per segment definition via segmentDefinitions[].mediaSources. For plain prompt Q&A on an already-indexed video, sync-analyse-video is faster (Pegasus 1.2, returns inline). Use that when you already have a videoId. This tool is fire-and-forget: it returns a taskId and status immediately. Poll status with get-analyse-task (every 5-10s; a 2-hour video may take several minutes). When status is "ready", the result lives in the task response. Input rules: - Provide exactly one of videoUrl, assetId, or base64Video. - If using assetId, ensure the asset status is "ready" first (assets still processing will be rejected). - videoUrl must be a direct http(s) link to raw media — YouTube/Drive/Dropbox share links are not accepted. - base64Video max 30 MB encoded; prefer URL or asset for larger inputs. - prompt drives general (prompt-based) analysis on either model. It cannot be combined with analysisMode="time_based_metadata". - analysisMode="time_based_metadata" requires modelName="pegasus1.5" (the default) and segmentDefinitions. - segmentDefinitions requires analysisMode="time_based_metadata" and selects structured per-segment output. - jsonSchema (optional) constrains general-mode output to structured JSON (JSON Schema Draft 2020-12 subset). Cannot be combined with segmentDefinitions. 1.2.4 additions (all optional): - promptV2: structured prompt with <@name> image references (Pegasus 1.5 only). Mutually exclusive with prompt. - startTime / endTime: clip the analysis window to a sub-range (Pegasus 1.5 only). Mutually exclusive with segmentDefinition.timeRanges. - segmentDefinition.timeRanges: restrict TBM extraction to specific time windows. Mutually exclusive with top-level startTime/endTime and min/maxSegmentDuration. - customId: caller-supplied identifier (1-64 chars, [A-Za-z0-9_-]) returned in task responses.. It is categorised as a Read tool in the Twelvelabs Mcp Server MCP Server, which means it retrieves data without modifying state.
Register the Twelvelabs Mcp Server MCP server in PolicyLayer and add a rule for async-analyse-video: 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 Twelvelabs Mcp Server. Nothing to install.
async-analyse-video 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 async-analyse-video 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 async-analyse-video. 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.
async-analyse-video is provided by the Twelvelabs Mcp Server MCP server (https://mcp.twelvelabs.io). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 24 Twelvelabs Mcp Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.