nrc.reactor.current_status
Get the latest daily power output for all ~95 US commercial nuclear reactor units as reported by the US Nuclear Regulatory Commission (NRC). Returns each reactor's current power level as a percentage of licensed thermal power (0–100%), operational status (full_power / reduced_power / shutdown), a...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/nrc.reactor.current-status.md
What nrc.reactor.current_status does on Apibase
AI agents call nrc.reactor.current_status 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 |
|---|---|---|---|
sort_by | string | — | Sort order for the reactor list. "name" (alphabetical, default), "power_asc" (lowest power first), "power_desc" (highest power first). |
Parameters from the server's own tool schema.
Why nrc.reactor.current_status is rated Low
Retrieves public nuclear reactor status data from NRC without side effects or modifications.
From the tool's definition Get the latest daily power output, current power level, operational status, fleet-wide summary counts
Attacks that exploit this kind of access
The rule that runs nrc.reactor.current_status 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 nrc.reactor.current_status, this is the rule to start with:
nrc.reactor.current_status 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 nrc.reactor.current_status call is checked against it from then on.
Questions about nrc.reactor.current_status
Get the latest daily power output for all ~95 US commercial nuclear reactor units as reported by the US Nuclear Regulatory Commission (NRC). Returns each reactor's current power level as a percentage of licensed thermal power (0–100%), operational status (full_power / reduced_power / shutdown), and fleet-wide summary counts. Data is updated each business day M–F and reflects the previous day's reported capacity. Essential for US energy grid monitoring, nuclear generation capacity dashboards, and power market analysis. No auth — US NRC public domain data (Atomic Energy Act), unlimited free. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
nrc.reactor.current_status accepts 1 parameter: sort_by. 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 nrc.reactor.current_status: 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.
nrc.reactor.current_status 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 nrc.reactor.current_status 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 nrc.reactor.current_status. 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.
nrc.reactor.current_status 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