transcribe_urls_batch · Whipscribe MCP: Risk & Policy

WHAT IT DOES

What transcribe_urls_batch does on Whipscribe

AI agents invoke transcribe_urls_batch to trigger actions in Whipscribe. 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 transcribe_urls_batch needs a policy

This tool triggers external transcription operations on multiple URLs concurrently, which involves executing network requests and processing pipelines on external services. It is not a simple read (it initiates jobs/operations), not purely write (it runs processing), and the batch/concurrent nature increases blast radius if misused with many URLs.

From the tool's definition Transcribe a list of URLs (YouTube, podcast, direct media) concurrently

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

transcribe_urls_batch Rate-limited

transcribe_urls_batch 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": {
    "transcribe_urls_batch": {
      "limits": [
        {
          "counter": "transcribe_urls_batch_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 Whipscribe, so you can run agents against it safely.

FAQ

Questions about transcribe_urls_batch

What does the transcribe_urls_batch tool do? +

Transcribe a list of URLs (YouTube, podcast, direct media) concurrently. It is categorised as a Execute tool in the Whipscribe MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on transcribe_urls_batch? +

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

What risk level is transcribe_urls_batch? +

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

Can I rate-limit transcribe_urls_batch? +

Yes. Add a rate_limit block to the transcribe_urls_batch 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 transcribe_urls_batch completely? +

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

transcribe_urls_batch is provided by the Whipscribe MCP server (neugence/whipscribe-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.