concat_videos
POST /v5/tools/concat_videos. Current Bannerbear V5 operation; provider scopes, locks and credits apply. Mandatory confirmation before provider execution; one submission only.
This record as markdown: /tools/thenavidm-bannerbear-mcp-cli/concat-videos.md
What concat_videos does on Bannerbear Mcp Cli
AI agents call concat_videos to retrieve information from Bannerbear Mcp Cli without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
account | string | — | Exact private workspace profile label; no fallback to another profile key. |
confirm | boolean | — | Set true only when the user asked for exactly this action. |
payload | object | — | Complete current native JSON body. Use payload or payload_file exclusively. |
payload_file | string | — | Regular non-symlink local JSON file, at most 1 MiB. |
Parameters from the server's own tool schema.
Why concat_videos is rated Low
Even though concat_videos only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsAccepts raw HTML/template content (payload) · High parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs concat_videos safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Bannerbear Mcp Cli, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For concat_videos, this is the rule to start with:
concat_videos is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Bannerbear Mcp Cli, apply this rule, and every concat_videos call is checked against it from then on.
Questions about concat_videos
POST /v5/tools/concat_videos. Current Bannerbear V5 operation; provider scopes, locks and credits apply. Mandatory confirmation before provider execution; one submission only. It is categorised as a Read tool in the Bannerbear Mcp Cli MCP Server, which means it retrieves data without modifying state.
concat_videos accepts 4 parameters: account, confirm, payload, payload_file. The full parameter table on this page comes from the server's own tool schema.
Register the Bannerbear Mcp Cli MCP server in PolicyLayer and add a rule for concat_videos: 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 Bannerbear Mcp Cli. Nothing to install.
concat_videos 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 concat_videos 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 concat_videos. 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.
concat_videos is provided by the Bannerbear Mcp Cli MCP server (@thenavidm/bannerbear-mcp-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Bannerbear Mcp Cli, and thousands of servers like it.
This server
Across the catalogue