Get comprehensive cooking guidance for a specific protein including target temperatures, time estimates, and tips. This is the primary tool for planning a cook. It provides: - Target internal temperature based on desired doneness - Pull temperature (accounting for carryover) - Estimated cook time...
AI agents call bbq_get_cooking_guidance to retrieve information from BBQ MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is purely an informational/advisory tool that returns cooking recommendations based on input parameters. It does not execute commands, modify data, perform financial transactions, or trigger external operations. The integration with ThermoWorks Cloud is read-only (monitoring/analysis). The tool simply assembles and returns guidance, making it a classic Read category tool with low risk.
From the tool's definition The tool 'bbq_get_cooking_guidance' retrieves and provides information: 'target internal temperature', 'estimated cook time', 'timeline', 'stall warnings', 'resting instructions', and 'pro tips'.
Attacks that exploit this kind of access
Get comprehensive cooking guidance for a specific protein including target temperatures, time estimates, and tips. This is the primary tool for planning a cook. It provides: - Target internal temperature based on desired doneness - Pull temperature (accounting for carryover) - Estimated cook time based on weight and method - Timeline for when to start if serving time is specified - Stall warnings for large cuts - Resting instructions - Pro tips for the specific protein Args: - protein_type: Type of meat (e.g.,. It is categorised as a Read tool in the BBQ MCP Server MCP Server, which means it retrieves data without modifying state.
Register the BBQ MCP Server MCP server in PolicyLayer and add a rule for bbq_get_cooking_guidance: 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 BBQ MCP Server. Nothing to install.
bbq_get_cooking_guidance 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 bbq_get_cooking_guidance 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 bbq_get_cooking_guidance. 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.
bbq_get_cooking_guidance is provided by the BBQ MCP Server MCP server (jweingardt12/bbq-mcp). 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 →