getEVCharger
Get electric vehicle charging stations near a location specified by latitude and longitude coordinates.
This record as markdown: /tools/com-api-ninjas-mcp/getevcharger.md
What getEVCharger does on API Ninjas
AI agents call getEVCharger 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 |
|---|---|---|---|
lat | number | Yes | Latitude coordinate. |
lon | number | Yes | Longitude coordinate. |
level | integer | — | Charging level (1, 2, or 3). By default, all levels are returned. |
limit | integer | — | How many results to return. Must be between 1 and 30. Default is 3. |
offset | integer | — | Number of results to skip. Used for pagination. Default is 0. |
distance | integer | — | Search distance in kilometers. Default is 3 kilometers. Max value is 50 kilometers. |
Parameters from the server's own tool schema.
Why getEVCharger is rated Low
Even though getEVCharger 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 getEVCharger 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 getEVCharger, this is the rule to start with:
getEVCharger 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 getEVCharger call is checked against it from then on.
Questions about getEVCharger
Get electric vehicle charging stations near a location specified by latitude and longitude coordinates. It is categorised as a Read tool in the API Ninjas MCP Server, which means it retrieves data without modifying state.
getEVCharger accepts 6 parameters: lat, lon, level, limit, offset, distance. Required: lat, lon. 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 getEVCharger: 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.
getEVCharger 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 getEVCharger 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 getEVCharger. 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.
getEVCharger 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