nrel.afdc.detail
Get detailed record for one specific alt-fuel station by its AFDC station ID — operator info, full address, hours per day-of-week, EV charging speed breakdown (Level 1/2/DC Fast outlet counts), accepted payment methods, access restrictions.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/nrel.afdc.detail.md
What nrel.afdc.detail does on Apibase
AI agents call nrel.afdc.detail 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 |
|---|---|---|---|
station_id | integer | Yes | AFDC station ID (positive integer). Obtained from afdc_stations_nearest or afdc_stations_search results. |
Parameters from the server's own tool schema.
Why nrel.afdc.detail is rated Low
Retrieves publicly available alternative fuel station information with no data modification or side effects.
From the tool's definition Get detailed record for one specific alt-fuel station by its AFDC station ID
Attacks that exploit this kind of access
The rule that runs nrel.afdc.detail 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.detail, this is the rule to start with:
nrel.afdc.detail 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.detail call is checked against it from then on.
Questions about nrel.afdc.detail
Get detailed record for one specific alt-fuel station by its AFDC station ID — operator info, full address, hours per day-of-week, EV charging speed breakdown (Level 1/2/DC Fast outlet counts), accepted payment methods, access restrictions. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
nrel.afdc.detail accepts 1 parameter: station_id. Required: station_id. 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.detail: 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.detail 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.detail 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.detail. 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.detail 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