find_component_usages

THE RISK

Low Risk

Why find_component_usages needs a policy

This tool performs a read-only search/discovery operation within a FlutterFlow project cache. It retrieves information about component usage across pages but does not create, modify, delete, or execute any code. The explicit statement of 'cache-only' and 'no API calls' confirms it has no side effects. This fits squarely within the Read category (search, list, get, fetch operations).

From the tool's definition Tool description explicitly states 'Find all pages and components where a given component is used' and 'Cache-only, no API calls', indicating retrieval and querying of existing project data with no side effects.

Documented attack patterns abuse exactly the kind of access find_component_usages gives an agent:

POLICY

How to control find_component_usages

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_component_usages:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "find_component_usages": {}
  }
}

find_component_usages is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Community Ff — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Community Ff tools

Write sync_project Sync an entire FlutterFlow project to the local cache. Downloads all YAML files (bulk or b Write update_project_yaml Push YAML changes to a FlutterFlow project. IMPORTANT: Always call validate_yaml first to Read find_page_navigations Find all actions that navigate to a given page, showing source page, trigger, disabled sta Read get_api_endpoints Get API endpoint definitions from local cache — method, URL, variables, headers, response Read get_app_settings Get App Settings — Authentication, Push Notifications, Mobile Deployment (version, build, Read get_app_state Get app state variables, constants, and environment settings from local cache. No API call Read get_component_summary Get a readable summary of a FlutterFlow component from local cache — widget tree, actions, Read get_custom_code Get custom actions, functions, widgets, AI agents, app action components, and custom files

All 25 Community Ff tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about find_component_usages

What does the find_component_usages tool do? +

Find all pages and components where a given component is used, with parameter pass details. 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.

How do I enforce a policy on find_component_usages? +

Register the Community Ff MCP server in PolicyLayer and add a rule for find_component_usages: 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.

What risk level is find_component_usages? +

find_component_usages is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit find_component_usages? +

Yes. Add a rate_limit block to the find_component_usages 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.

How do I block find_component_usages completely? +

Set action: deny in the PolicyLayer policy for find_component_usages. 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.

What MCP server provides find_component_usages? +

find_component_usages 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.

Enforce policy on every Community Ff tool call.

Start from Community Ff, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →