update_workflow

PATCH /v5/workflows/{uid}. Current Bannerbear V5 operation; provider scopes, locks and credits apply. Mandatory confirmation before provider execution; one submission only.

SERVERBannerbear Mcp Cli SOURCE@thenavidm/bannerbear-mcp-cli

Medium RISK CLASS

Category Write

Parameters 51 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/thenavidm-bannerbear-mcp-cli/update-workflow.md

WHAT IT DOES

What update_workflow does on Bannerbear Mcp Cli

AI agents use update_workflow 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
`uid`	string	Yes
`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.

RISK

Why update_workflow is rated Medium

An AI agent can call update_workflow 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) · High parameter count (14 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_workflow 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 update_workflow, this is the rule to start with:

update_workflow Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_workflow": {
      "limits": [
        {
          "counter": "update_workflow_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Bannerbear Mcp Cli, apply this rule, and every update_workflow call is checked against it from then on.

FAQ

Questions about update_workflow

What does the update_workflow tool do? +

PATCH /v5/workflows/{uid}. 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.

What parameters does update_workflow accept? +

update_workflow accepts 5 parameters: uid, account, confirm, payload, payload_file. Required: uid. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_workflow? +

Register the Bannerbear Mcp Cli MCP server in PolicyLayer and add a rule for update_workflow: 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.

What risk level is update_workflow? +

update_workflow is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_workflow? +

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

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

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

KEEP EXPLORING

More on Bannerbear Mcp Cli, and thousands of servers like it.

This server

All 75 Bannerbear Mcp Cli tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →