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

resolve_resist_element

Resolve a declared clerical Resist Fire or Resist Cold on exactly one touched living creature. The ward lasts one turn per cleric level. Multiclass casters must supply their exact cleric level.

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/resolve-resist-element.md

What resolve_resist_element does on Torch-to-Crown

AI agents use resolve_resist_element 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_resist_element is rated Medium

An AI agent can call resolve_resist_element 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 resolve_resist_element

What does the resolve_resist_element tool do? +

Resolve a declared clerical Resist Fire or Resist Cold on exactly one touched living creature. The ward lasts one turn per cleric level. Multiclass casters must supply their exact cleric level. 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 resolve_resist_element? +

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

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

Can I rate-limit resolve_resist_element? +

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

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

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