Find EV charging stations (electric vehicle chargers) near a place. Pass a location name (city/place, e.g. "San Francisco", "Berlin", "Austin TX") and it is geocoded automatically — OR pass explicit latitude+longitude. Returns nearby charging stations with operator, status, available connector ty...
AI agents call find_stations to retrieve information from Mcp Openchargemap without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
_apiKey | string | — | Optional — your own Open Charge Map API key for higher limits; works without one. |
country | string | — | Optional ISO country code (e.g. "US", "FR") to disambiguate an ambiguous `location` like "Paris" or "Springfield". |
distance | number | — | Search radius around the location (default 10). |
latitude | number | — | Latitude of the search center, e.g. 37.7749. Optional if `location` is given. |
location | string | — | Place/city name to search near, e.g. "San Francisco", "Berlin", "Austin TX". Geocoded automatically. Provide THIS or latitude+longitude. |
longitude | number | — | Longitude of the search center, e.g. -122.4194. Optional if `location` is given. |
max_results | number | — | Maximum number of stations to return (default 20, max 100). |
distance_unit | string | — | Unit for the search radius (default "KM"). |
connection_type | string | — | Optional connector type name to filter by, e.g. "CCS", "CHAdeMO", "Tesla". Case-insensitive substring match against each station's connector titles. |
Parameters from the server's own tool schema.
This tool queries a public database (Open Charge Map) to retrieve and display charging station locations and metadata. It performs passive data retrieval based on location input (geocoded from place name or explicit coordinates). There is no data creation, modification, deletion, code execution, or financial transaction. The tool has no destructive capability and cannot change system state.
From the tool's definition Tool description states it "Find[s] EV charging stations" and "Returns nearby charging stations with operator, status, available connector types... and distance." Key verbs are 'find' and 'returns' — retrieval operations with no modification or side effects.
Attacks that exploit this kind of access
Find EV charging stations (electric vehicle chargers) near a place. Pass a location name (city/place, e.g. "San Francisco", "Berlin", "Austin TX") and it is geocoded automatically — OR pass explicit latitude+longitude. Returns nearby charging stations with operator, status, available connector types (CCS/CHAdeMO/Tesla connectors), charging speed (kW), and distance. Filter by connector type to find e.g. only CCS or Tesla chargers. It is categorised as a Read tool in the Mcp Openchargemap MCP Server, which means it retrieves data without modifying state.
find_stations accepts 9 parameters: _apiKey, country, distance, latitude, location, longitude, max_results, distance_unit, connection_type. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Openchargemap MCP server in PolicyLayer and add a rule for find_stations: 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 Mcp Openchargemap. Nothing to install.
find_stations 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 find_stations 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 find_stations. 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.
find_stations is provided by the Mcp Openchargemap MCP server (https://gateway.pipeworx.io/openchargemap/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →