Google Flow Browser MCP

17 tools. 10 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated:

10 can modify or destroy data
7 read-only
17 tools total

Community server · catalogue entry verified 12/06/2026

How to control Google Flow Browser MCP ↓

What Google Flow Browser MCP exposes to your agents

Read (7) Write / Execute (9) Destructive / Financial (1)
Critical Risk

The most dangerous Google Flow Browser MCP tools

10 of Google Flow Browser MCP's 17 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control Google Flow Browser MCP

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. These are the rules we recommend:

Block financial tools by default
{
  "flow_generate_image": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Requires human approval."
      }
    ]
  }
}

Financial tools should be explicitly enabled per use case, not open by default.

Rate limit write operations
{
  "flow_create_character": {
    "limits": [
      {
        "counter": "flow_create_character_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "flow_account_check": {
    "limits": [
      {
        "counter": "flow_account_check_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register Google Flow Browser MCP — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON GOOGLE FLOW BROWSER →

Free to start. No card required.

All 17 Google Flow Browser MCP tools

Questions about Google Flow Browser MCP

Can an AI agent move money through the Google Flow Browser MCP server? +

Yes. The Google Flow Browser MCP server exposes 1 financial tools including flow_generate_image. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.

How do I prevent bulk modifications through Google Flow Browser MCP? +

The Google Flow Browser MCP server has 3 write tools including flow_create_character, flow_create_scene, flow_import_character. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Google Flow Browser MCP.

How many tools does the Google Flow Browser MCP server expose? +

17 tools across 2 categories: Read, Write. 7 are read-only. 10 can modify, create, or delete data.

How do I enforce a policy on Google Flow Browser MCP? +

Register the Google Flow Browser MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Google Flow Browser MCP tool call.

Deterministic rules across all 17 Google Flow Browser MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

17 Google Flow Browser MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.