resolve_anti_plant_shell
Complete a declared Anti-Plant Shell as an immobile 80ft-radius sphere or hemisphere for one turn per druid level. Classify every creature by whether its body or carried gear contains vegetable matter. Shared movement blocks classified matter, and the attack tool blocks vegetable missiles such as...
This record as markdown: /tools/torch-to-crown/resolve-anti-plant-shell.md
What resolve_anti_plant_shell does on Torch-to-Crown
AI agents use resolve_anti_plant_shell 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_anti_plant_shell is rated Medium
An AI agent can call resolve_anti_plant_shell 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_anti_plant_shell 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_anti_plant_shell, this is the rule to start with:
resolve_anti_plant_shell 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_anti_plant_shell call is checked against it from then on.
Questions about resolve_anti_plant_shell
Complete a declared Anti-Plant Shell as an immobile 80ft-radius sphere or hemisphere for one turn per druid level. Classify every creature by whether its body or carried gear contains vegetable matter. Shared movement blocks classified matter, and the attack tool blocks vegetable missiles such as wooden arrows. 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_anti_plant_shell: 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_anti_plant_shell 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_anti_plant_shell 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_anti_plant_shell. 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_anti_plant_shell 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