create_batch
POST /v5/batches. 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/create-batch.md
What create_batch does on Bannerbear Mcp Cli
AI agents use create_batch to create or update resources in Bannerbear Mcp Cli, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bannerbear Mcp Cli environment.
| 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 create_batch is rated Medium
An AI agent can call create_batch faster than any human can review: one bad instruction and it creates or modifies resources in Bannerbear Mcp Cli by the hundred, each call as confident as the last.
Risk signalsAccepts raw HTML/template content (payload)
Attacks that exploit this kind of access
The rule that runs create_batch 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 create_batch, this is the rule to start with:
create_batch stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 create_batch call is checked against it from then on.
Questions about create_batch
POST /v5/batches. Current Bannerbear V5 operation; provider scopes, locks and credits apply. Mandatory confirmation before provider execution; one submission only. It is categorised as a Write tool in the Bannerbear Mcp Cli MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_batch 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 create_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 Bannerbear Mcp Cli. Nothing to install.
create_batch is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_batch 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