AI agents use end_encounter to create or update resources in ChatRPG — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ChatRPG environment.
This tool modifies game state by concluding an encounter and recording outcomes, making it a Write operation. It is not Read (it modifies state beyond mere querying), not Execute (it doesn't run arbitrary code or trigger unpredictable external effects), not Destructive (encounter logs are preserved and outcomes can be reviewed/changed in a new encounter), not Financial, and not Other.
From the tool's definition Tool description states 'End a combat encounter with outcome tracking and optional summary generation' and 'Can preserve encounter log for review.' These are reversible state modifications within the game context—marking an encounter as ended and optionally…
Attacks that exploit this kind of access
End a combat encounter with outcome tracking and optional summary generation. Supports victory, defeat, fled, negotiated outcomes. Can preserve encounter log for review. It is categorised as a Write tool in the ChatRPG MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ChatRPG MCP server in PolicyLayer and add a rule for end_encounter: 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 ChatRPG. Nothing to install.
end_encounter 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 end_encounter 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 end_encounter. 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.
end_encounter is provided by the ChatRPG MCP server (mnehmos/mnehmos.chatrpg.game). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →