Create a new scene in Google Flow Scenes with characters and prompt.
AI agents use flow_create_scene to create or update resources in Google Flow Browser MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Flow Browser MCP environment.
This tool creates new data structures (scenes) within Google Flow, making it a Write operation. The severity is medium because while the tool enables content generation that could be misused (e.g., creating numerous scenes to consume resources or generate unwanted content), the effects are reversible and don't involve deletion, execution of arbitrary code, or financial impact.
From the tool's definition Tool description states 'Create a new scene' which is a create operation that modifies data in Google Flow. The action is reversible (scenes can be deleted or modified), and it involves setting up characters and prompts within the Google Flow platform.
Documented attack patterns abuse exactly the kind of access flow_create_scene gives an agent:
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_create_scene:
{
"version": "1",
"default": "deny",
"tools": {
"flow_create_scene": {
"limits": [
{
"counter": "flow_create_scene_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}flow_create_scene 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.
Free to start. No card required.
Create a new scene in Google Flow Scenes with characters and prompt. It is categorised as a Write tool in the Google Flow Browser MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Flow Browser MCP server in PolicyLayer and add a rule for flow_create_scene: 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.
flow_create_scene 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 flow_create_scene 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 flow_create_scene. 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.
flow_create_scene 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.
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.
Free to start. No card required.
17 Google Flow Browser MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.