Fetch a FlutterFlow page by its human-readable name (e.g.
AI agents call get_page_by_name 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 and returns data about a specific FlutterFlow page. The verb 'fetch' combined with the lack of any write, execute, or destructive capability indicates a read-only operation. The context (alongside sibling tools like get_component_summary, get_data_models, get_api_endpoints) confirms this is part of a read-focused exploration API for understanding FlutterFlow projects.
From the tool's definition Tool name 'get_page_by_name' and description 'Fetch a FlutterFlow page by its human-readable name' indicate a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_page_by_name 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 get_page_by_name:
{
"version": "1",
"default": "deny",
"tools": {
"get_page_by_name": {}
}
}get_page_by_name 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.
Fetch a FlutterFlow page by its human-readable name (e.g. 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 get_page_by_name: 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.
get_page_by_name 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 get_page_by_name 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 get_page_by_name. 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.
get_page_by_name 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.