spoonacular.recipes.by_ingredients
Find recipes using ingredients you have on hand — shows used/missing ingredients count, ranked by ingredient match (Spoonacular)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/spoonacular.recipes.by-ingredients.md
What spoonacular.recipes.by_ingredients does on Apibase
AI agents call spoonacular.recipes.by_ingredients to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
number | integer | — | Number of results to return (default 10, max 100) |
ranking | integer | — | Ranking mode: 1 = maximize used ingredients, 2 = minimize missing ingredients (default 1) |
ingredients | string | Yes | Comma-separated list of ingredients you have (e.g. "chicken,rice,tomato") |
ignore_pantry | boolean | — | Ignore common pantry items like water, flour, salt (default false) |
Parameters from the server's own tool schema.
Why spoonacular.recipes.by_ingredients is rated Low
Tool queries recipe data with no side effects; returns ranked results based on search criteria.
From the tool's definition Find recipes using ingredients, shows ingredient match count
Attacks that exploit this kind of access
The rule that runs spoonacular.recipes.by_ingredients safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For spoonacular.recipes.by_ingredients, this is the rule to start with:
spoonacular.recipes.by_ingredients is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every spoonacular.recipes.by_ingredients call is checked against it from then on.
Questions about spoonacular.recipes.by_ingredients
Find recipes using ingredients you have on hand — shows used/missing ingredients count, ranked by ingredient match (Spoonacular). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
spoonacular.recipes.by_ingredients accepts 4 parameters: number, ranking, ingredients, ignore_pantry. Required: ingredients. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for spoonacular.recipes.by_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 Apibase. Nothing to install.
spoonacular.recipes.by_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 spoonacular.recipes.by_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 spoonacular.recipes.by_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.
spoonacular.recipes.by_ingredients is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue