Read YAML files from the local project cache. Requires sync_project to be run first. Returns one file if fileName is specified, or lists all cached file keys if omitted.
AI agents call get_project_yaml 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 reads existing project configuration files without modifying, executing, or deleting anything. It is a straightforward data retrieval operation on cached YAML files, consistent with the 'Read' category. The blast radius of misuse is minimal—the worst outcome would be disclosure of project configuration data already present locally.
From the tool's definition Tool description explicitly states 'Read YAML files from the local project cache' and 'Returns one file if fileName is specified, or lists all cached file keys if omitted.' The verbs 'read,' 'returns,' and 'lists' indicate retrieval-only operations with no…
Documented attack patterns abuse exactly the kind of access get_project_yaml 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_project_yaml:
{
"version": "1",
"default": "deny",
"tools": {
"get_project_yaml": {}
}
}get_project_yaml 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.
Read YAML files from the local project cache. Requires sync_project to be run first. Returns one file if fileName is specified, or lists all cached file keys if omitted. 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_project_yaml: 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_project_yaml 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_project_yaml 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_project_yaml. 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_project_yaml 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.