twelvelabs_analyze · Open MCP Knowledgebase MCP

WHAT IT DOES

What twelvelabs_analyze does on Open MCP Knowledgebase

AI agents invoke twelvelabs_analyze to trigger actions in Open MCP Knowledgebase. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why twelvelabs_analyze needs a policy

This tool executes an external API operation against a third-party video intelligence service (TwelveLabs), making it Execute rather than Read. While it retrieves analytical results, it actively triggers processing on an external platform rather than simply querying static data. Severity is medium because misuse could expose video content to unintended analysis or leak prompts to an external service.

From the tool's definition 'Analyze a specific video using the TwelveLabs integration' — triggers an external video analysis operation via a third-party service (TwelveLabs).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

twelvelabs_analyze Rate-limited

twelvelabs_analyze stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "twelvelabs_analyze": {
      "limits": [
        {
          "counter": "twelvelabs_analyze_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Open MCP Knowledgebase, so you can run agents against it safely.

FAQ

Questions about twelvelabs_analyze

What does the twelvelabs_analyze tool do? +

Analyze a specific video using the TwelveLabs integration bound to a content scope. Call list_integrations first and obtain video ids from scoped search results. Prompt bodies and raw index ids are not logged or returned by default. It is categorised as a Execute tool in the Open MCP Knowledgebase MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on twelvelabs_analyze? +

Register the Open MCP Knowledgebase MCP server in PolicyLayer and add a rule for twelvelabs_analyze: 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 Open MCP Knowledgebase. Nothing to install.

What risk level is twelvelabs_analyze? +

twelvelabs_analyze is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit twelvelabs_analyze? +

Yes. Add a rate_limit block to the twelvelabs_analyze 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.

How do I block twelvelabs_analyze completely? +

Set action: deny in the PolicyLayer policy for twelvelabs_analyze. 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.

What MCP server provides twelvelabs_analyze? +

twelvelabs_analyze is provided by the Open MCP Knowledgebase MCP server (no-product/knowledgebase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.