ev.charging.nearby
Find the nearest EV charging stations to GPS coordinates within a radius (default 5km). Returns stations sorted by distance with connector types, power levels, and availability status. Filter by minimum power kW and connector type for DC fast charging (Open Charge Map)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/ev.charging.nearby.md
What ev.charging.nearby does on Apibase
AI agents call ev.charging.nearby 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 |
|---|---|---|---|
limit | integer | — | Maximum results (1-50, default 10) |
radius | number | — | Search radius in KM (default 5) |
latitude | number | Yes | GPS latitude of your location (e.g. 40.7128) |
longitude | number | Yes | GPS longitude of your location (e.g. -74.0060) |
min_power_kw | number | — | Minimum charger power in kW (e.g. 50 for DC fast charging) |
connection_type_id | integer | — | Filter by connector type (25=Type 2, 33=CCS, 2=CHAdeMO) |
Parameters from the server's own tool schema.
Why ev.charging.nearby is rated Low
Tool queries public EV charging station data; retrieves location and status information with no side effects or modifications.
From the tool's definition Find the nearest EV charging stations to GPS coordinates. Returns stations sorted by distance with connector types, power levels, and availability status.
Attacks that exploit this kind of access
The rule that runs ev.charging.nearby 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 ev.charging.nearby, this is the rule to start with:
ev.charging.nearby 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 ev.charging.nearby call is checked against it from then on.
Questions about ev.charging.nearby
Find the nearest EV charging stations to GPS coordinates within a radius (default 5km). Returns stations sorted by distance with connector types, power levels, and availability status. Filter by minimum power kW and connector type for DC fast charging (Open Charge Map). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
ev.charging.nearby accepts 6 parameters: limit, radius, latitude, longitude, min_power_kw, connection_type_id. Required: latitude, longitude. 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 ev.charging.nearby: 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.
ev.charging.nearby 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 ev.charging.nearby 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 ev.charging.nearby. 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.
ev.charging.nearby 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