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.

SERVERLivedatalink SOURCEhttps://livedatalink.ai/mcp
Low RISK CLASS
Category Read
Parameters 80 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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

This tool performs a location-based search/lookup to retrieve information about alternative fuel stations. It has no side effects beyond data retrieval. While used by route planning and fleet operators, the tool itself only returns informational results to support decision-making; it does not execute commands, modify any systems, or commit financial transactions.

From the tool's definition Tool description states it 'Find[s] alternative fuel stations near a location' - a query operation that retrieves data about fuel station locations and types. No creation, modification, deletion, code execution, or financial operations are described.

Questions about nrel_alt_fuel_stations

What does the nrel_alt_fuel_stations tool do? +

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.

What parameters does nrel_alt_fuel_stations accept? +

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.

How do I enforce a policy on nrel_alt_fuel_stations? +

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.

What risk level is nrel_alt_fuel_stations? +

nrel_alt_fuel_stations is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit nrel_alt_fuel_stations? +

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.

How do I block nrel_alt_fuel_stations completely? +

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.

What MCP server provides nrel_alt_fuel_stations? +

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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Livedatalink's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.