flee_combat
Spend a declared flee action. Every able melee opponent within 10ft makes one immediate attack at +4 even if it already acted; a survivor then moves up to its normal movement rate. Set parry true when the armed fugitive parries those fleeing attacks, subtracting positive Strength and weapon-speci...
This record as markdown: /tools/torch-to-crown/flee-combat.md
What flee_combat does on Torch-to-Crown
AI agents use flee_combat 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 flee_combat is rated Medium
An AI agent can call flee_combat 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 flee_combat 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 flee_combat, this is the rule to start with:
flee_combat 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 flee_combat call is checked against it from then on.
Questions about flee_combat
Spend a declared flee action. Every able melee opponent within 10ft makes one immediate attack at +4 even if it already acted; a survivor then moves up to its normal movement rate. Set parry true when the armed fugitive parries those fleeing attacks, subtracting positive Strength and weapon-specialisation hit bonuses. 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 flee_combat: 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.
flee_combat 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 flee_combat 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 flee_combat. 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.
flee_combat 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