New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

nrel.afdc.search

Search US alt-fuel stations by ZIP, state, or city. Filterable by fuel type, EV network, connector type, and access level. Use for state-level analytics or city-wide EV infrastructure surveys; use afdc_stations_nearest for proximity search to a coordinate.

SERVERApibase SOURCEapibase-mcp-client
Low RISK CLASS
Category Read
Parameters 90 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/nrel.afdc.search.md

What nrel.afdc.search does on Apibase

AI agents call nrel.afdc.search 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.

ParameterTypeRequiredDescription
zip string — 5-digit US ZIP code to search within. Example: '94102'.
city string — City name. Use with state for disambiguation. Example: Oakland.
limit integer — Results per page (1-200). Default 50.
state string — 2-letter US state code. Example: 'CA', 'TX', 'NY'.
access string — Filter by access type: 'public' for open-access stations, 'private' for fleet-only.
offset integer — Pagination offset — number of results to skip. Default 0.
status string — Station status: E=available (open), P=planned (future), T=temporarily unavailable. Default E.
fuel_type string — Comma-separated fuel codes: ELEC (electric), CNG, LNG, LPG (propane), BD (biodiesel), E85, HY (hydrogen). Default ELEC.
ev_connector_type string — EV connector codes (comma-separated): J1772 (Level 2), J1772COMBO (CCS), CHADEMO, TESLA, NEMA1450, NEMA515.

Parameters from the server's own tool schema.

Why nrel.afdc.search is rated Low

Tool queries public EV infrastructure data without modifying, deleting, or executing operations.

From the tool's definition Search US alt-fuel stations by ZIP, state, or city. Filterable by fuel type, EV network, connector type.

Questions about nrel.afdc.search

What does the nrel.afdc.search tool do? +

Search US alt-fuel stations by ZIP, state, or city. Filterable by fuel type, EV network, connector type, and access level. Use for state-level analytics or city-wide EV infrastructure surveys; use afdc_stations_nearest for proximity search to a coordinate. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does nrel.afdc.search accept? +

nrel.afdc.search accepts 9 parameters: zip, city, limit, state, access, offset, status, fuel_type, ev_connector_type. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on nrel.afdc.search? +

Register the Apibase MCP server in PolicyLayer and add a rule for nrel.afdc.search: 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.

What risk level is nrel.afdc.search? +

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

Can I rate-limit nrel.afdc.search? +

Yes. Add a rate_limit block to the nrel.afdc.search 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.afdc.search completely? +

Set action: deny in the PolicyLayer policy for nrel.afdc.search. 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.afdc.search? +

nrel.afdc.search 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.

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 Apibase'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.