spoonacular.recipes.search
Search 365K+ recipes with dietary filters (vegan, keto, gluten-free), cuisine, meal type, and max prep time — includes nutrition data per result (Spoonacular)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/spoonacular.recipes.search.md
What spoonacular.recipes.search does on Apibase
AI agents call spoonacular.recipes.search 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 |
|---|---|---|---|
diet | string | — | Diet filter: gluten free, ketogenic, vegetarian, lacto-vegetarian, ovo-vegetarian, vegan, pescetarian, paleo, primal, whole30 |
type | string | — | Meal type: main course, side dish, dessert, appetizer, salad, bread, breakfast, soup, beverage, sauce, marinade, fingerfood, snack, drink |
query | string | — | Search query for recipes (e.g. "pasta", "chicken soup") |
number | integer | — | Number of results to return (default 10, max 100) |
offset | integer | — | Offset for pagination (default 0) |
cuisine | string | — | Cuisine filter — comma-separated (e.g. "italian", "mexican,chinese") |
intolerances | string | — | Intolerances filter — comma-separated (e.g. "dairy,gluten,peanut,shellfish") |
max_ready_time | integer | — | Maximum preparation time in minutes |
Parameters from the server's own tool schema.
Why spoonacular.recipes.search is rated Low
Queries recipe data without modifying, deleting, or executing external operations.
From the tool's definition Search 365K+ recipes with filters, includes nutrition data per result
Attacks that exploit this kind of access
The rule that runs spoonacular.recipes.search 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.search, this is the rule to start with:
spoonacular.recipes.search 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.search call is checked against it from then on.
Questions about spoonacular.recipes.search
Search 365K+ recipes with dietary filters (vegan, keto, gluten-free), cuisine, meal type, and max prep time — includes nutrition data per result (Spoonacular). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
spoonacular.recipes.search accepts 8 parameters: diet, type, query, number, offset, cuisine, intolerances, max_ready_time. 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.search: 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.search 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.search 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.search. 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.search 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