Get all raw assignments for a specific variable in a .bb or .bbappend file.
AI agents call get_recipe_var_raw 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 tool performs data retrieval from recipe files without side effects. It queries and extracts variable data from configuration files without creating, modifying, deleting, or executing code. The deterministic parsing of static file content poses minimal risk, limited to information disclosure of recipe contents.
From the tool's definition Tool retrieves and extracts 'raw variable assignments from .bb and .bbappend files without performing variable evaluation.' The description explicitly states it 'get[s] all raw assignments' - a read operation with no modification, deletion, or execution…
Attacks that exploit this kind of access
Get all raw assignments for a specific variable in a .bb or .bbappend file. 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 get_recipe_var_raw: 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.
get_recipe_var_raw 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_recipe_var_raw 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_recipe_var_raw. 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_recipe_var_raw 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 →