Find all actions that navigate to a given page, showing source page, trigger, disabled status, and passed parameters. Cache-only, no API calls. Run sync_project first.
AI agents call find_page_navigations to retrieve information from Community Ff without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool purely retrieves and queries navigation metadata from a FlutterFlow project's cached structure. It returns information about existing page navigation actions without modifying, executing, or deleting any project data. The 'cache-only' designation confirms no side effects beyond reading. Severity is low because disclosure of navigation structure poses minimal risk even if misused.
From the tool's definition Tool description states it 'Find[s] all actions that navigate to a given page' with read-only outputs (source page, trigger, disabled status, parameters). Explicitly noted as 'Cache-only, no API calls' indicating data retrieval only.
Documented attack patterns abuse exactly the kind of access find_page_navigations gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Community Ff, and nothing reaches the server without passing your rules. This is the rule we recommend for find_page_navigations:
{
"version": "1",
"default": "deny",
"tools": {
"find_page_navigations": {}
}
}find_page_navigations 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.
Find all actions that navigate to a given page, showing source page, trigger, disabled status, and passed parameters. Cache-only, no API calls. Run sync_project first. It is categorised as a Read tool in the Community Ff MCP Server, which means it retrieves data without modifying state.
Register the Community Ff MCP server in PolicyLayer and add a rule for find_page_navigations: 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 Community Ff. Nothing to install.
find_page_navigations 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 find_page_navigations 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 find_page_navigations. 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.
find_page_navigations is provided by the Community Ff MCP server (mohn93/ff-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Community Ff, 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.
25 Community Ff tools catalogued and risk-classified — across an index of 43,000+ MCP servers.