nrc.reactor.outages
Identify US nuclear reactors currently operating below a specified power threshold. By default returns all reactors not at full power (below 100%). Set max_power=0 to see only fully-shutdown reactors, or max_power=50 to find reactors at half-power or less. Results include power percentage and sta...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/nrc.reactor.outages.md
What nrc.reactor.outages does on Apibase
AI agents use nrc.reactor.outages to create or update resources in Apibase, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apibase environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
max_power | integer | — | Maximum power percentage threshold (inclusive, 0–100). Returns reactors at or below this level. Default 99 returns all reactors not at full power (100%). Set to |
Parameters from the server's own tool schema.
Why nrc.reactor.outages is rated Medium
An AI agent can call nrc.reactor.outages faster than any human can review: one bad instruction and it creates or modifies resources in Apibase by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs nrc.reactor.outages 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.outages, this is the rule to start with:
nrc.reactor.outages stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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.outages call is checked against it from then on.
Questions about nrc.reactor.outages
Identify US nuclear reactors currently operating below a specified power threshold. By default returns all reactors not at full power (below 100%). Set max_power=0 to see only fully-shutdown reactors, or max_power=50 to find reactors at half-power or less. Results include power percentage and status (reduced_power or shutdown) sorted lowest-power first. Useful for energy grid impact assessment, nuclear capacity risk monitoring, and real-time tracking of planned and unplanned reactor outages across the US fleet. No auth — US NRC public domain data (Atomic Energy Act), unlimited free. It is categorised as a Write tool in the Apibase MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
nrc.reactor.outages accepts 1 parameter: max_power. 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.outages: 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.outages is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the nrc.reactor.outages 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.outages. 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.outages 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