Find EV charging stations nearby. Filter by network (Tesla, IONITY, Trugo, ChargePoint, etc.), connector type, country, and minimum power. Covers Turkey (Trugo/Togg, Eşarj, ZES, Sharz.net), US (Tesla, Electrify America, ChargePoint, EVgo), and Europe (IONITY, Fastned, Shell, BP Pulse).
AI agents call ev_charging to retrieve information from Yaver without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
lat | number | Yes | |
lon | number | Yes | |
radius | integer | — | Search radius in km (default: 10) |
country | string | — | Country code or name (e.g. TR, turkey, US, DE) |
network | string | — | Network filter: tesla, ionity, chargepoint, evgo, shell, bp |
min_power_kw | integer | — | Minimum charging power in kW (e.g. 50 for DC fast only) |
connector_type | string | — | Connector type ID (use ev_connector_types to see list) |
Parameters from the server's own tool schema.
Even though ev_charging 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
Find EV charging stations nearby. Filter by network (Tesla, IONITY, Trugo, ChargePoint, etc.), connector type, country, and minimum power. Covers Turkey (Trugo/Togg, Eşarj, ZES, Sharz.net), US (Tesla, Electrify America, ChargePoint, EVgo), and Europe (IONITY, Fastned, Shell, BP Pulse). It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
ev_charging accepts 7 parameters: lat, lon, radius, country, network, min_power_kw, connector_type. Required: lat, lon. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for ev_charging: 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 Yaver. Nothing to install.
ev_charging 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 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. 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 is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.