New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

cast_legend_lore

Spend Legend Lore, destroy its recorded valuable focus, roll the exact focus-dependent casting time, advance campaign time, and preserve only referee-authored legendary material or its absence.

SERVERTorch-to-Crown SOURCEDiogenes187/Torch-to-Crown
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/torch-to-crown/cast-legend-lore.md

What cast_legend_lore does on Torch-to-Crown

AI agents call cast_legend_lore 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_legend_lore is rated Critical

An AI agent that decides to call cast_legend_lore 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.

Questions about cast_legend_lore

What does the cast_legend_lore tool do? +

Spend Legend Lore, destroy its recorded valuable focus, roll the exact focus-dependent casting time, advance campaign time, and preserve only referee-authored legendary material or its absence. 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.

How do I enforce a policy on cast_legend_lore? +

Register the Torch-to-Crown MCP server in PolicyLayer and add a rule for cast_legend_lore: 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.

What risk level is cast_legend_lore? +

cast_legend_lore is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit cast_legend_lore? +

Yes. Add a rate_limit block to the cast_legend_lore 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.

How do I block cast_legend_lore completely? +

Set action: deny in the PolicyLayer policy for cast_legend_lore. 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.

What MCP server provides cast_legend_lore? +

cast_legend_lore 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Torch-to-Crown's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.