resolve_enlarge_creature
Resolve declared Enlarge on one positioned living creature: +20% size and weight per magic-user level (maximum +200%), one turn per level, 5ft range per level, and at most 10 cubic ft of living matter per level. Unwilling targets save against the exact Spells (unlisted categories) column; willing...
This record as markdown: /tools/torch-to-crown/resolve-enlarge-creature.md
What resolve_enlarge_creature does on Torch-to-Crown
AI agents use resolve_enlarge_creature 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_enlarge_creature is rated Medium
An AI agent can call resolve_enlarge_creature 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_enlarge_creature 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_enlarge_creature, this is the rule to start with:
resolve_enlarge_creature 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_enlarge_creature call is checked against it from then on.
Questions about resolve_enlarge_creature
Resolve declared Enlarge on one positioned living creature: +20% size and weight per magic-user level (maximum +200%), one turn per level, 5ft range per level, and at most 10 cubic ft of living matter per level. Unwilling targets save against the exact Spells (unlisted categories) column; willing targets forego it. The source prints no general attack/damage bonus. Reduce and non-living objects remain explicitly unsupported because their durable representation and the reverse. 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_enlarge_creature: 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_enlarge_creature 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_enlarge_creature 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_enlarge_creature. 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_enlarge_creature 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