nrel.afdc.nearest
Find the nearest alternative fuel stations to a given US location (latitude/longitude). Includes EV charging (Level 1/2/DC Fast), CNG, LNG, propane, biodiesel, hydrogen. Returns station name, address, network, plug types, hours, last verified date. US-specific; for global EV stations use openchar...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/nrel.afdc.nearest.md
What nrel.afdc.nearest does on Apibase
AI agents call nrel.afdc.nearest 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 | — | Max stations to return (1-200). Default 20. |
radius | number | — | Search radius in miles (max 500). Default 5. |
status | string | — | Station status: E=available (open), P=planned (future), T=temporarily unavailable. Default E. |
latitude | number | Yes | WGS84 latitude (US territory only). Example: 37.7749 for San Francisco. |
fuel_type | string | — | Comma-separated fuel codes: ELEC (electric), CNG, LNG, LPG (propane), BD (biodiesel), E85, HY (hydrogen). Default ELEC. |
longitude | number | Yes | WGS84 longitude (US territory only). Example: -122.4194 for San Francisco. |
Parameters from the server's own tool schema.
Why nrel.afdc.nearest is rated Low
Tool queries public fuel station location data with no side effects or data modification capabilities.
From the tool's definition Find the nearest alternative fuel stations to a given US location. Returns station name, address, network.
Attacks that exploit this kind of access
The rule that runs nrel.afdc.nearest 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 nrel.afdc.nearest, this is the rule to start with:
nrel.afdc.nearest 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 nrel.afdc.nearest call is checked against it from then on.
Questions about nrel.afdc.nearest
Find the nearest alternative fuel stations to a given US location (latitude/longitude). Includes EV charging (Level 1/2/DC Fast), CNG, LNG, propane, biodiesel, hydrogen. Returns station name, address, network, plug types, hours, last verified date. US-specific; for global EV stations use openchargemap. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
nrel.afdc.nearest accepts 6 parameters: limit, radius, status, latitude, fuel_type, longitude. 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 nrel.afdc.nearest: 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.
nrel.afdc.nearest 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 nrel.afdc.nearest 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 nrel.afdc.nearest. 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.
nrel.afdc.nearest 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