resolve_globe_of_invulnerability
Resolve a declared self-centred 5ft-radius globe for one round per magic-user level. Minor hedges out spell levels 1–3; major hedges out levels 1–4. Spells cast from inside pass outward, and Dispel Magic destroys the globe automatically. Spell declaration centrally filters protected targets for e...
This record as markdown: /tools/torch-to-crown/resolve-globe-of-invulnerability.md
What resolve_globe_of_invulnerability does on Torch-to-Crown
AI agents use resolve_globe_of_invulnerability 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_globe_of_invulnerability is rated Medium
An AI agent can call resolve_globe_of_invulnerability 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.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs resolve_globe_of_invulnerability 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_globe_of_invulnerability, this is the rule to start with:
resolve_globe_of_invulnerability 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_globe_of_invulnerability call is checked against it from then on.
Questions about resolve_globe_of_invulnerability
Resolve a declared self-centred 5ft-radius globe for one round per magic-user level. Minor hedges out spell levels 1–3; major hedges out levels 1–4. Spells cast from inside pass outward, and Dispel Magic destroys the globe automatically. Spell declaration centrally filters protected targets for every automatic, dedicated, and adjudicated route. 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_globe_of_invulnerability: 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_globe_of_invulnerability 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_globe_of_invulnerability 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_globe_of_invulnerability. 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_globe_of_invulnerability 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