getCarGenerations
The level most vehicle APIs do not expose. Optional: nothing downstream requires it. Generations with no cars are returned with car_count 0 so gaps are visible. Requires a Business or Professional plan, or any annual plan.
This record as markdown: /tools/com-api-ninjas-mcp/getcargenerations.md
What getCarGenerations does on API Ninjas
AI agents call getCarGenerations 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 |
|---|---|---|---|
make | string | — | Manufacturer, as a word. Case and punctuation are ignored, so bmw, BMW and Bmw all resolve. |
year | integer | — | Only generations in production in this year. |
limit | integer | — | How many results to return, between 1 and 100. Default 30. A value outside that range is rejected rather than silently clamped. |
model | string | — | Model, as a word. '3 Series', '3-series' and '3series' all resolve. |
offset | integer | — | Number of results to skip, for pagination. Default 0. |
has_cars | boolean | — | Set true to omit generations that have no cars. |
chassis_code | string | — | Filter to one chassis code, e.g. E91. Matches anything whose chassis_codes contains it. |
Parameters from the server's own tool schema.
Why getCarGenerations is rated Low
Even though getCarGenerations 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 getCarGenerations 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 getCarGenerations, this is the rule to start with:
getCarGenerations 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 getCarGenerations call is checked against it from then on.
Questions about getCarGenerations
The level most vehicle APIs do not expose. Optional: nothing downstream requires it. Generations with no cars are returned with car_count 0 so gaps are visible. Requires a Business or Professional plan, or any annual plan. It is categorised as a Read tool in the API Ninjas MCP Server, which means it retrieves data without modifying state.
getCarGenerations accepts 7 parameters: make, year, limit, model, offset, has_cars, chassis_code. 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 getCarGenerations: 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.
getCarGenerations 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 getCarGenerations 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 getCarGenerations. 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.
getCarGenerations 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