resolve_dispel
Resolve a declared cleric, druid, or magic-user Dispel Magic, or illusionist Dispel Illusion. Supply each ongoing combat condition in the chosen area with its originating caster level because legacy condition records do not store that level. The engine rolls the printed independent 50% check, adj...
This record as markdown: /tools/torch-to-crown/resolve-dispel.md
What resolve_dispel does on Torch-to-Crown
AI agents use resolve_dispel 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 resolve_dispel is rated Medium
An AI agent can call resolve_dispel 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.
Attacks that exploit this kind of access
The rule that runs resolve_dispel 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 resolve_dispel, this is the rule to start with:
resolve_dispel stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 resolve_dispel call is checked against it from then on.
Questions about resolve_dispel
Resolve a declared cleric, druid, or magic-user Dispel Magic, or illusionist Dispel Illusion. Supply each ongoing combat condition in the chosen area with its originating caster level because legacy condition records do not store that level. The engine rolls the printed independent 50% check, adjusted +5% per level the dispeller is higher or -2% per level lower. Mark automatic only for the caster. 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.
Register the Torch-to-Crown MCP server in PolicyLayer and add a rule for resolve_dispel: 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.
resolve_dispel is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the resolve_dispel 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 resolve_dispel. 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.
resolve_dispel 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.
This server
Across the catalogue