getElectricVehicleData
Returns electric vehicle records with range, battery, charging, and performance data, filtered by make, model, year, or range. For maker names use /electricvehiclemakes.
This record as markdown: /tools/com-api-ninjas-mcp/getelectricvehicledata.md
What getElectricVehicleData does on API Ninjas
AI agents call getElectricVehicleData 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 | — | Vehicle manufacturer (e.g., tesla or nissan) |
limit | integer | — | How many results to return. Must be between 1 and 10. Default is 1. |
model | string | — | Vehicle model. Supports partial matching (e.g., 'Model' matches 'Model 3', 'Model Y', etc.). |
offset | integer | — | Number of results to skip. Used for pagination. Default is 0. |
max_year | integer | — | Maximum vehicle model year (e.g., 2023) |
min_year | integer | — | Minimum vehicle model year (e.g., 2020) |
max_range | integer | — | Maximum range in kilometers (e.g., 400) |
min_range | integer | — | Minimum range in kilometers (e.g., 250) |
Parameters from the server's own tool schema.
Why getElectricVehicleData is rated Low
Even though getElectricVehicleData 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 getElectricVehicleData 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 getElectricVehicleData, this is the rule to start with:
getElectricVehicleData 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 getElectricVehicleData call is checked against it from then on.
Questions about getElectricVehicleData
Returns electric vehicle records with range, battery, charging, and performance data, filtered by make, model, year, or range. For maker names use /electricvehiclemakes. It is categorised as a Read tool in the API Ninjas MCP Server, which means it retrieves data without modifying state.
getElectricVehicleData accepts 8 parameters: make, limit, model, offset, max_year, min_year, max_range, min_range. 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 getElectricVehicleData: 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.
getElectricVehicleData 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 getElectricVehicleData 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 getElectricVehicleData. 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.
getElectricVehicleData 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