Get custom actions, functions, widgets, AI agents, app action components, and custom files from local cache — signatures, arguments, return types, and optionally Dart source code. No API calls. Run sync_project first if not cached.
AI agents call get_custom_code 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 queries cached FlutterFlow project data (custom code, signatures, metadata) without creating, modifying, deleting, or executing anything. It is purely informational/exploratory, consistent with the server's stated purpose of 'reading, exploring, and understanding' projects. The sibling tools (find_*, get_*) follow the same read-only pattern, reinforcing the classification.
From the tool's definition Tool description explicitly states it 'Get[s] custom actions, functions, widgets' and 'No API calls,' and retrieves data 'from local cache' with 'signatures, arguments, return types.' The verb 'Get' and read-only nature confirm retrieval without side effects.
Documented attack patterns abuse exactly the kind of access get_custom_code 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_custom_code:
{
"version": "1",
"default": "deny",
"tools": {
"get_custom_code": {}
}
}get_custom_code 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.
Get custom actions, functions, widgets, AI agents, app action components, and custom files from local cache — signatures, arguments, return types, and optionally Dart source code. No API calls. Run sync_project first if not cached. 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_custom_code: 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_custom_code 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_custom_code 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_custom_code. 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_custom_code 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.