Sync an entire FlutterFlow project to the local cache. Downloads all YAML files (bulk or batched fallback) for fast offline reads. Use force=true to re-sync an already cached project.
AI agents use sync_project to create or update resources in Community Ff — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Community Ff environment.
This tool downloads and writes data to a local cache. While it reads from the remote FlutterFlow project, it writes/overwrites local files. It is reversible (re-syncing or clearing cache), so it falls under Write rather than Destructive. The force=true flag could overwrite cached data but does not irreversibly destroy source data.
From the tool's definition Sync an entire FlutterFlow project to the local cache. Downloads all YAML files (bulk or batched fallback) for fast offline reads.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access sync_project 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 sync_project:
{
"version": "1",
"default": "deny",
"tools": {
"sync_project": {
"limits": [
{
"counter": "sync_project_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}sync_project stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Sync an entire FlutterFlow project to the local cache. Downloads all YAML files (bulk or batched fallback) for fast offline reads. Use force=true to re-sync an already cached project. It is categorised as a Write tool in the Community Ff MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Community Ff MCP server in PolicyLayer and add a rule for sync_project: 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.
sync_project is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the sync_project 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 sync_project. 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.
sync_project 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.