Start a twelvelabs video indexing task. This will allow the video to be used by the embedding model and searched in natural language. If no indexId is provided, we will add the video to the default index. You can provide either a videoUrl (for remote videos), a videoFilePath (for local video file...
Part of the Twelvelabs Mcp Server server.
Free to start. No card required.
AI agents invoke start-video-indexing-task to trigger processes or run actions in Twelvelabs Mcp Server. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
start-video-indexing-task can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"start-video-indexing-task": {
"limits": [
{
"counter": "start-video-indexing-task_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Twelvelabs Mcp Server policy for all 24 tools.
These attack patterns abuse exactly the kind of access start-video-indexing-task gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Start a twelvelabs video indexing task. This will allow the video to be used by the embedding model and searched in natural language. If no indexId is provided, we will add the video to the default index. You can provide either a videoUrl (for remote videos), a videoFilePath (for local video files), or a folderFilePath (to index all videos in a local folder). If both videoUrl and videoFilePath are provided, we will use the videoUrl. Supports Google Drive links (file or folder). For Google Drive folders, all MP4 videos will be indexed and multiple tasks will be started. You can also pass optional userMetadata as a JSON string of key-value pairs to attach metadata to the indexed video(s).. It is categorised as a Execute tool in the Twelvelabs Mcp Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Twelvelabs Mcp Server MCP server in PolicyLayer and add a rule for start-video-indexing-task: 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.
start-video-indexing-task is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the start-video-indexing-task 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 start-video-indexing-task. 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.
start-video-indexing-task 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.