Verify the logged-in Google account matches the configured expected email (Profile 3).
AI agents call flow_account_check to retrieve information from Google Flow Browser MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and compares account identity information. No data is created, modified, deleted, or irreversibly changed. No code execution, financial transaction, or destructive action occurs. It is a simple identity verification check, making it a Read operation with low severity since the blast radius of misuse (confirming which account is logged in) is minimal.
From the tool's definition Tool verifies/checks the logged-in Google account against a configured email. The verb 'verify' and 'check' indicate a query operation that retrieves account information without modification.
Documented attack patterns abuse exactly the kind of access flow_account_check 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_account_check:
{
"version": "1",
"default": "deny",
"tools": {
"flow_account_check": {}
}
} flow_account_check is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Verify the logged-in Google account matches the configured expected email (Profile 3). It is categorised as a Read tool in the Google Flow Browser MCP MCP Server, which means it retrieves data without modifying state.
Register the Google Flow Browser MCP server in PolicyLayer and add a rule for flow_account_check: 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_account_check 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 flow_account_check 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_account_check. 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_account_check 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.