cast_atonement
Spend one prepared clerical Atonement and perform its exact one-turn touch cleansing. Intentional acts are refused; repentance or an explicit incapacity is required; non-true-neutral clerics ordinarily must share an alignment axis. The operation can permanently restore an explicitly confirmed mag...
This record as markdown: /tools/torch-to-crown/cast-atonement.md
What cast_atonement does on Torch-to-Crown
AI agents call cast_atonement to permanently remove resources in Torch-to-Crown, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why cast_atonement is rated Critical
An AI agent that decides to call cast_atonement doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Torch-to-Crown is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs cast_atonement safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Torch-to-Crown, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cast_atonement, this is the rule to start with:
cast_atonement is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Torch-to-Crown, apply this rule, and every cast_atonement call is checked against it from then on.
Questions about cast_atonement
Spend one prepared clerical Atonement and perform its exact one-turn touch cleansing. Intentional acts are refused; repentance or an explicit incapacity is required; non-true-neutral clerics ordinarily must share an alignment axis. The operation can permanently restore an explicitly confirmed magically altered alignment and end target-matched consequences explicitly marked Atonement-eligible. It is categorised as a Destructive tool in the Torch-to-Crown MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Torch-to-Crown MCP server in PolicyLayer and add a rule for cast_atonement: 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 Torch-to-Crown. Nothing to install.
cast_atonement is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cast_atonement 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 cast_atonement. 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.
cast_atonement is provided by the Torch-to-Crown MCP server (Diogenes187/Torch-to-Crown). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Torch-to-Crown, and thousands of servers like it.
Across the catalogue