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

continue_exorcism

Spend the next uninterrupted turn on an active Exorcise effect and make its saved modified d% check. The caster cannot voluntarily halt the procedure.

SERVERTorch-to-Crown SOURCEDiogenes187/Torch-to-Crown
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/torch-to-crown/continue-exorcism.md

What continue_exorcism does on Torch-to-Crown

AI agents use continue_exorcism to create or update resources in Torch-to-Crown, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Torch-to-Crown environment.

Why continue_exorcism is rated Medium

An AI agent can call continue_exorcism faster than any human can review: one bad instruction and it creates or modifies resources in Torch-to-Crown by the hundred, each call as confident as the last.

Questions about continue_exorcism

What does the continue_exorcism tool do? +

Spend the next uninterrupted turn on an active Exorcise effect and make its saved modified d% check. The caster cannot voluntarily halt the procedure. It is categorised as a Write tool in the Torch-to-Crown MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on continue_exorcism? +

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

continue_exorcism is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit continue_exorcism? +

Yes. Add a rate_limit block to the continue_exorcism 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 continue_exorcism completely? +

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

continue_exorcism 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

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