Search cached project file keys by keyword, prefix, or regex. Returns matching file keys for use with get_project_yaml. Cache-only, no API calls. Run sync_project first.
AI agents call search_project_files 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 performs a search operation on cached project file keys, which is a read-only retrieval operation. It has no side effects—it does not create, modify, delete, or execute any code. The explicit statement that it is 'cache-only, no API calls' reinforces that it only queries existing data. This is clearly a Read category tool with low severity since misuse would only expose cached metadata about project files.
From the tool's definition Search cached project file keys by keyword, prefix, or regex. Returns matching file keys. Cache-only, no API calls. The tool retrieves/queries cached data without modification, deletion, or execution.
Documented attack patterns abuse exactly the kind of access search_project_files 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 search_project_files:
{
"version": "1",
"default": "deny",
"tools": {
"search_project_files": {}
}
}search_project_files 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.
Search cached project file keys by keyword, prefix, or regex. Returns matching file keys for use with get_project_yaml. 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.
Register the Community Ff MCP server in PolicyLayer and add a rule for search_project_files: 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.
search_project_files 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 search_project_files 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 search_project_files. 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.
search_project_files 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.