nrc.reactor.annual_data
Retrieve full-year historical power status data for US nuclear reactors from NRC annual archives. Data is available from 1999 through the current year. Optionally filter by reactor unit name to retrieve a single reactor's complete year record. Each record contains the date, unit name, and power p...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/nrc.reactor.annual-data.md
What nrc.reactor.annual_data does on Apibase
AI agents call nrc.reactor.annual_data 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 |
|---|---|---|---|
unit | string | — | Optional reactor unit name filter (e.g. "Palo Verde 1"). When provided, returns only records for that reactor. Case-insensitive. |
year | integer | — | Calendar year for the historical archive (1999–current year). Defaults to the current year. Annual files contain daily snapshots for all ~95 US reactors. |
limit | integer | — | Maximum number of rows to return (1–1000). Defaults to 200. The full annual file may contain 17K–35K rows. |
Parameters from the server's own tool schema.
Why nrc.reactor.annual_data is rated Low
Retrieves publicly available historical nuclear reactor operational data without modification or control capabilities.
From the tool's definition Retrieve full-year historical power status data for US nuclear reactors from NRC annual archives.
Attacks that exploit this kind of access
The rule that runs nrc.reactor.annual_data 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.annual_data, this is the rule to start with:
nrc.reactor.annual_data 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.annual_data call is checked against it from then on.
Questions about nrc.reactor.annual_data
Retrieve full-year historical power status data for US nuclear reactors from NRC annual archives. Data is available from 1999 through the current year. Optionally filter by reactor unit name to retrieve a single reactor's complete year record. Each record contains the date, unit name, and power percentage (0–100%). Supports capacity factor analysis, long-term outage pattern research, nuclear energy generation modeling, and historical grid impact studies. Returns up to 1000 rows per call (full annual files contain 17K–35K rows). 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.annual_data accepts 3 parameters: unit, year, limit. 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.annual_data: 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.annual_data 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.annual_data 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.annual_data. 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.annual_data 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