getRecipes
Get a list of recipes for a given recipe name or ingredient(s). Returns a list of recipes with nutrition information when available. To access more results, use the limit parameter to limit the number of results and the offset parameter to offset results for pagination in multiple API calls.
This record as markdown: /tools/com-api-ninjas-mcp/getrecipes.md
What getRecipes does on API Ninjas
AI agents call getRecipes to retrieve information from API Ninjas 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 |
|---|---|---|---|
limit | integer | — | Number of results to return. Must be between 1 and 10. If not set, a default value of 1 will be used. Premium subscribers only. |
title | string | — | Recipe title to search for. |
offset | integer | — | Number of results to offset for pagination. Premium subscribers only. |
ingredients | string | — | Comma-separated list of ingredients to search for. Premium subscribers only. |
Parameters from the server's own tool schema.
Why getRecipes is rated Low
Even though getRecipes only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs getRecipes safely
PolicyLayer is an MCP gateway: it sits between your AI agents and API Ninjas, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getRecipes, this is the rule to start with:
getRecipes 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 API Ninjas, apply this rule, and every getRecipes call is checked against it from then on.
Questions about getRecipes
Get a list of recipes for a given recipe name or ingredient(s). Returns a list of recipes with nutrition information when available. To access more results, use the limit parameter to limit the number of results and the offset parameter to offset results for pagination in multiple API calls. It is categorised as a Read tool in the API Ninjas MCP Server, which means it retrieves data without modifying state.
getRecipes accepts 4 parameters: limit, title, offset, ingredients. The full parameter table on this page comes from the server's own tool schema.
Register the API Ninjas MCP server in PolicyLayer and add a rule for getRecipes: 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 API Ninjas. Nothing to install.
getRecipes 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 getRecipes 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 getRecipes. 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.
getRecipes is provided by the API Ninjas MCP server (https://mcp.api-ninjas.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on API Ninjas, and thousands of servers like it.
This server
Across the catalogue