batch_create_clips

THE RISK

High Risk

Why batch_create_clips needs a policy

This tool triggers a batch export/rendering operation that processes multiple video clips simultaneously, producing output files. This constitutes an external operation (video encoding/rendering pipeline) with real resource consumption and file system side effects. It's not purely Write since it executes a media processing pipeline, and not Destructive since it creates new files rather than deleting.

From the tool's definition Export multiple clips at once as finished vertical shorts

Risk signalsBulk/mass operation — affects multiple targets

Documented attack patterns abuse exactly the kind of access batch_create_clips gives an agent:

POLICY

How to control batch_create_clips

PolicyLayer is an MCP gateway — it sits between your AI agents and Podcli, and nothing reaches the server without passing your rules. This is the rule we recommend for batch_create_clips:

policy.json

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

batch_create_clips 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.

Create a free account and register Podcli — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Podcli tools

Execute parse_transcript Parse a raw speaker-labeled plain text transcript into word-level timestamps. Input format Execute transcribe_podcast STEP 1 — Transcribe a podcast video/audio file. This is typically the first tool you call. Write create_clip STEP 3 — Export a single clip as a finished vertical short (1080x1920, 9:16).\n\n Write import_transcript Import an external transcript (e.g. from a transcription service) into the UI. Skips Whisp Write knowledge_base Read or manage the podcli knowledge base. These are .md files that provide context about t Write manage_assets Register and manage reusable assets (logos, videos). Registered assets can be referenced b Write manage_presets Save, load, list, or delete rendering presets. Presets store caption_style, crop_strategy, Write modify_clip Adjust a suggested clip before exporting. Change timing, title, or caption style.

All 17 Podcli tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Podcli → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about batch_create_clips

What does the batch_create_clips tool do? +

STEP 3 — Export multiple clips at once as finished vertical shorts.\n\n. It is categorised as a Execute tool in the Podcli MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on batch_create_clips? +

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

What risk level is batch_create_clips? +

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

Can I rate-limit batch_create_clips? +

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

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

batch_create_clips is provided by the Podcli MCP server (nmbrthirteen/podcli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Podcli tool call.

Start from Podcli, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →