List all pages in a FlutterFlow project with human-readable names, scaffold IDs, and folder assignments. Use this FIRST to discover pages before fetching their YAML.
AI agents call list_pages 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 retrieves information about pages in a FlutterFlow project without creating, modifying, deleting, or executing any operations. It is a safe read-only operation with minimal blast radius if misused by an agent—the worst outcome would be exposure of project structure metadata.
From the tool's definition Tool name 'list_pages' and description 'List all pages in a FlutterFlow project' indicates data retrieval with no modification. The phrase 'discover pages before fetching their YAML' confirms it is a lookup/discovery operation.
Documented attack patterns abuse exactly the kind of access list_pages 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 list_pages:
{
"version": "1",
"default": "deny",
"tools": {
"list_pages": {}
}
} list_pages 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.
List all pages in a FlutterFlow project with human-readable names, scaffold IDs, and folder assignments. Use this FIRST to discover pages before fetching their YAML. 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 list_pages: 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.
list_pages 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 list_pages 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 list_pages. 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.
list_pages 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.