evaluate_haleu_transport_cask_safety
Evaluates Type B transport cask decay heat dissipation, radiation dose rates, and criticality safety margins for HALEU Category II SNM shipments.
This record as markdown: /tools/oklo-aurora-mcp/evaluate-haleu-transport-cask-safety.md
What evaluate_haleu_transport_cask_safety does on Oklo Aurora
AI agents call evaluate_haleu_transport_cask_safety as a supporting operation in Oklo Aurora workflows.
Why evaluate_haleu_transport_cask_safety is rated Low
Without any rule in front of it, every call an agent makes to evaluate_haleu_transport_cask_safety happens silently: no trail, no cap, no way to know it misbehaved until something breaks downstream.
Attacks that exploit this kind of access
The rule that runs evaluate_haleu_transport_cask_safety safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Oklo Aurora, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For evaluate_haleu_transport_cask_safety, this is the rule to start with:
evaluate_haleu_transport_cask_safety gets a rate cap, and everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Oklo Aurora, apply this rule, and every evaluate_haleu_transport_cask_safety call is checked against it from then on.
Questions about evaluate_haleu_transport_cask_safety
Evaluates Type B transport cask decay heat dissipation, radiation dose rates, and criticality safety margins for HALEU Category II SNM shipments. It is categorised as a Other tool in the Oklo Aurora MCP Server, which means it performs auxiliary operations.
Register the Oklo Aurora MCP server in PolicyLayer and add a rule for evaluate_haleu_transport_cask_safety: 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 Oklo Aurora. Nothing to install.
evaluate_haleu_transport_cask_safety is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the evaluate_haleu_transport_cask_safety 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 evaluate_haleu_transport_cask_safety. 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.
evaluate_haleu_transport_cask_safety is provided by the Oklo Aurora MCP server (petjal/oklo-aurora-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Oklo Aurora, and thousands of servers like it.
This server
Across the catalogue