trigger_drain_glyph
Discharge the level-15 Drain glyph. Every selected creature saves versus Spells; failure loses one complete experience level or Hit Die, resets saved-character XP to the beginning of the new level, immediately reprofiles combat attacks/saves/spell capacity, and kills a creature drained below leve...
This record as markdown: /tools/torch-to-crown/trigger-drain-glyph.md
What trigger_drain_glyph does on Torch-to-Crown
AI agents invoke trigger_drain_glyph to trigger actions in Torch-to-Crown. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why trigger_drain_glyph is rated High
trigger_drain_glyph triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs trigger_drain_glyph 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 trigger_drain_glyph, this is the rule to start with:
trigger_drain_glyph stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Torch-to-Crown, apply this rule, and every trigger_drain_glyph call is checked against it from then on.
Questions about trigger_drain_glyph
Discharge the level-15 Drain glyph. Every selected creature saves versus Spells; failure loses one complete experience level or Hit Die, resets saved-character XP to the beginning of the new level, immediately reprofiles combat attacks/saves/spell capacity, and kills a creature drained below level or HD 1. It is categorised as a Execute tool in the Torch-to-Crown MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Torch-to-Crown MCP server in PolicyLayer and add a rule for trigger_drain_glyph: 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.
trigger_drain_glyph is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the trigger_drain_glyph 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 trigger_drain_glyph. 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.
trigger_drain_glyph 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