nrel_alt_fuel_stations
Find alternative fuel stations near a location: electric (EV) charging, CNG, LNG, E85, hydrogen, propane, biodiesel. Used by route planning agents, fleet operators, and EV/clean-fuel tech.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/nrel-alt-fuel-stations.md
What nrel_alt_fuel_stations does on Livedatalink
AI agents call nrel_alt_fuel_stations to retrieve information from Livedatalink 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 |
|---|---|---|---|
lat | number | — | Latitude. Use with lon as alternative to location. |
lon | number | — | Longitude. Use with lat as alternative to location. |
limit | number | — | Max stations to return (default 25, max 200). |
state | string | — | Optional 2-letter state code filter. |
radius | number | — | Search radius in miles (default 5, max 500). |
status | string | — | Optional status filter: E (available, default), P (planned), T (temporarily unavailable). |
location | string | — | Address or city/state. Either location OR lat+lon required. |
fuel_type | string | — | Comma-separated fuel types: ELEC (default), CNG, LNG, E85, HY, LPG, BD. |
Parameters from the server's own tool schema.
Why nrel_alt_fuel_stations is rated Low
Even though nrel_alt_fuel_stations 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
The rule that runs nrel_alt_fuel_stations safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For nrel_alt_fuel_stations, this is the rule to start with:
nrel_alt_fuel_stations 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 Livedatalink, apply this rule, and every nrel_alt_fuel_stations call is checked against it from then on.
Questions about nrel_alt_fuel_stations
Find alternative fuel stations near a location: electric (EV) charging, CNG, LNG, E85, hydrogen, propane, biodiesel. Used by route planning agents, fleet operators, and EV/clean-fuel tech. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
nrel_alt_fuel_stations accepts 8 parameters: lat, lon, limit, state, radius, status, location, fuel_type. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for nrel_alt_fuel_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 Livedatalink. Nothing to install.
nrel_alt_fuel_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 nrel_alt_fuel_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 nrel_alt_fuel_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.
nrel_alt_fuel_stations is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue