ev.charging.search
Search 300K+ EV charging stations worldwide by location, country, operator, connector type, and power level. Returns station address, GPS coordinates, connectors (Type 2, CCS, CHAdeMO), power kW, operator, status. Filter by min power for fast charging. Largest open EV charging database (Open Char...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/ev.charging.search.md
What ev.charging.search does on Apibase
AI agents call ev.charging.search 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 to return (1-100, default 20) |
distance | number | — | Search radius in distance_unit (default KM) |
latitude | number | — | Latitude for location-based search (e.g. 51.5074) |
longitude | number | — | Longitude for location-based search (e.g. -0.1278) |
operator_id | integer | — | Filter by charging network operator ID |
country_code | string | — | ISO 2-letter country code to filter by (e.g. "US", "GB", "DE") |
min_power_kw | number | — | Minimum charger power in kW (e.g. 50 for fast charging) |
distance_unit | string | — | Distance unit: KM or Miles (default KM) |
status_type_id | integer | — | Filter by status (50=Operational, 100=Not Operational) |
connection_type_id | integer | — | Filter by connector type (e.g. 25=Type 2, 33=CCS, 2=CHAdeMO) |
Parameters from the server's own tool schema.
Why ev.charging.search is rated Low
Tool queries a public EV charging database and returns informational data without modification or side effects.
From the tool's definition Search charging stations by location, country, operator, connector type, power level. Returns address, GPS, connectors, power, operator, status.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs ev.charging.search 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.search, this is the rule to start with:
ev.charging.search 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.search call is checked against it from then on.
Questions about ev.charging.search
Search 300K+ EV charging stations worldwide by location, country, operator, connector type, and power level. Returns station address, GPS coordinates, connectors (Type 2, CCS, CHAdeMO), power kW, operator, status. Filter by min power for fast charging. Largest open EV charging database (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.search accepts 10 parameters: limit, distance, latitude, longitude, operator_id, country_code, min_power_kw, distance_unit, status_type_id, connection_type_id. 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.search: 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.search 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.search 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.search. 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.search 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