nrc.reactor.history
Retrieve up to 365 days of daily power output history for a specific US nuclear reactor unit. Provide the full NRC unit name (e.g. "Diablo Canyon 1", "Watts Bar 2") and the number of days to look back. Returns a chronological series of power percentages and status labels, enabling trend analysis,...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/nrc.reactor.history.md
What nrc.reactor.history does on Apibase
AI agents call nrc.reactor.history 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 |
|---|---|---|---|
days | integer | — | Number of most-recent days to retrieve (1–365). Defaults to 30. Data is available for the last 365 calendar days. |
unit | string | Yes | Full NRC reactor unit name as it appears in the status report (e.g. "Arkansas Nuclear 1", "Diablo Canyon 2", "Watts Bar 1"). Case-insensitive. |
Parameters from the server's own tool schema.
Why nrc.reactor.history is rated Low
Queries public US NRC nuclear reactor operational data with no side effects or modifications.
From the tool's definition Retrieve daily power output history, chronological series, trend analysis, no modifications.
Attacks that exploit this kind of access
The rule that runs nrc.reactor.history 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.history, this is the rule to start with:
nrc.reactor.history 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.history call is checked against it from then on.
Questions about nrc.reactor.history
Retrieve up to 365 days of daily power output history for a specific US nuclear reactor unit. Provide the full NRC unit name (e.g. "Diablo Canyon 1", "Watts Bar 2") and the number of days to look back. Returns a chronological series of power percentages and status labels, enabling trend analysis, outage detection, maintenance window identification, and capacity factor calculation for individual reactors. Covers all units in the NRC 365-day rolling file. 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.history accepts 2 parameters: days, unit. Required: unit. 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.history: 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.history 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.history 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.history. 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.history 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