preview_render_batch
Local schema-validated 1–100 native image payload review. Digest binds exact order, method/path, profile label and body. No provider state or price validation.
This record as markdown: /tools/thenavidm-bannerbear-mcp-cli/preview-render-batch.md
What preview_render_batch does on Bannerbear Mcp Cli
AI agents call preview_render_batch 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 | — | |
payload | object | — | |
payload_file | string | — |
Parameters from the server's own tool schema.
Why preview_render_batch is rated Low
Even though preview_render_batch 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)
Attacks that exploit this kind of access
The rule that runs preview_render_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 preview_render_batch, this is the rule to start with:
preview_render_batch 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 preview_render_batch call is checked against it from then on.
Questions about preview_render_batch
Local schema-validated 1–100 native image payload review. Digest binds exact order, method/path, profile label and body. No provider state or price validation. It is categorised as a Read tool in the Bannerbear Mcp Cli MCP Server, which means it retrieves data without modifying state.
preview_render_batch accepts 3 parameters: account, 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 preview_render_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.
preview_render_batch 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 preview_render_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 preview_render_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.
preview_render_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