Get list of available ingredients
AI agents call get_ingredients to retrieve information from Kitchen MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or lists data (available ingredients) without creating, modifying, deleting, or executing any operations. It is a straightforward query operation with no ability to affect state. The low severity reflects minimal risk even if misused by an AI agent, as it only exposes informational data about ingredient availability.
From the tool's definition Tool name 'get_ingredients' with description 'Get list of available ingredients' indicates a retrieval operation with no side effects. The Kitchen MCP Server is a read-oriented service for querying food and recipe data.
Attacks that exploit this kind of access
Get list of available ingredients. It is categorised as a Read tool in the Kitchen MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kitchen MCP Server MCP server in PolicyLayer and add a rule for get_ingredients: 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 Kitchen MCP Server. Nothing to install.
get_ingredients 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_ingredients 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_ingredients. 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_ingredients is provided by the Kitchen MCP Server MCP server (paulabaal12/kitchen-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 →