Search recursively for .bb/.bbappend files matching a filename query under root_path.
AI agents call find_recipe_files to retrieve information from Mcp Bitbake without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a search/discovery tool that retrieves information about recipe files without modifying, executing, or deleting anything. It has no side effects and fits the Read category definition of 'retrieves or queries data.' Low severity because even if an AI agent misuses it to enumerate files, the blast radius is limited to information disclosure with no capability to alter system state.
From the tool's definition Tool searches recursively for .bb/.bbappend files matching a filename query. The description explicitly states it 'Search[es] recursively' with no mention of modification, deletion, or execution. Returns matching file paths only.
Attacks that exploit this kind of access
Search recursively for .bb/.bbappend files matching a filename query under root_path. It is categorised as a Read tool in the Mcp Bitbake MCP Server, which means it retrieves data without modifying state.
Register the Mcp Bitbake MCP server in PolicyLayer and add a rule for find_recipe_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 Mcp Bitbake. Nothing to install.
find_recipe_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 find_recipe_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 find_recipe_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.
find_recipe_files is provided by the Mcp Bitbake MCP server (pkt-lab/mcp-bitbake). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →