flow_generate_image

THE RISK

Critical Risk

Why flow_generate_image needs a policy

The tool explicitly states it consumes credits when generating images, making each invocation a financial commitment. Misuse by an AI agent could rapidly deplete a user's credit balance, placing this firmly in the Financial category with high severity.

From the tool's definition CES IMAGES CONSOMMENT DES CRÉDITS — 'these images consume credits', indicating financial cost per use

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

POLICY

How to control flow_generate_image

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "flow_generate_image": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

Any call to flow_generate_image is blocked until a human approves it. The rest of the server keeps working.

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

GATE THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Google Flow Browser MCP tools

Execute flow_connect Launch Chrome with the configured Google profile, connect CDP, navigate to Google Flow, an Execute flow_disconnect Close the browser and clean up the MCP connection to Google Flow. Execute flow_discover_ui Navigate to a Google Flow page and discover all interactive elements (buttons, inputs, lin Execute flow_generate_video Set up a video generation in Google Flow. Fills prompt, selects Omni Flash or Veo model, c Execute flow_use_grid_architect Open Grid Architect in Google Flow, fill theme prompt, shot prompts, engine, ratio, and vi Execute flow_use_tool Open any tool by name in Google Flow and optionally fill its configuration parameters. Write flow_create_character Create a new character in Google Flow Characters with name and description. Write flow_create_scene Create a new scene in Google Flow Scenes with characters and prompt.

All 17 Google Flow Browser MCP tools →

Financial tools on other servers

0xarchive web3_subscribe Math MCP Server financial_calculator MCP Kling generate_video MCP Uber Server uber_request_ride

Go deeper

Critical-risk tools in Google Flow Browser MCP → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-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.
Human-in-the-loop → When a tool call should wait for a person — and when policy can decide alone.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
How to Add Spending Controls to Any MCP Agent →
Rate Limiting MCP Tool Calls: A Practical Guide →

FAQ

Questions about flow_generate_image

What does the flow_generate_image tool do? +

⚠️ CES IMAGES CONSOMMENT DES CRÉDITS. Par défaut (auto_confirm=false): remplit le prompt, sélectionne le modèle/ratio, prend un screenshot et retourne. It is categorised as a Financial tool in the Google Flow Browser MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on flow_generate_image? +

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

What risk level is flow_generate_image? +

flow_generate_image is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit flow_generate_image? +

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

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

flow_generate_image is provided by the Google Flow Browser MCP server (tmsss05/google-flow-browser-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Google Flow Browser MCP tool call.

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

CHECK YOUR STACK →