manage_encounter · ChatRPG MCP: Risk & Policy

WHAT IT DOES

What manage_encounter does on ChatRPG

AI agents use manage_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.

WHY IT NEEDS A POLICY

Why manage_encounter needs a policy

This is primarily a Write tool because it creates encounters, updates participant states, and synchronizes data back to persistent character records. While it includes read operations (get, list), the core capability is reversible data modification ('create', 'end', 'commit').

From the tool's definition The tool performs state modification operations including 'create', 'get', 'end', 'commit', and 'list'. The description explicitly mentions 'state synchronization', 'participantUpdates', and 'sync to persistent characters', indicating the tool modifies…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

manage_encounter Rate-limited

manage_encounter 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "manage_encounter": {
      "limits": [
        {
          "counter": "manage_encounter_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches ChatRPG, so you can run agents against it safely.

FAQ

Questions about manage_encounter

What does the manage_encounter tool do? +

Composite tool for encounter management with state synchronization. Operations: create (with characterId linking), get (with verbosity), end (with participantUpdates), commit (sync to persistent characters), list (active encounters). Supports bridging encounter simulation state with persistent character records. 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.

How do I enforce a policy on manage_encounter? +

Register the ChatRPG MCP server in PolicyLayer and add a rule for manage_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.

What risk level is manage_encounter? +

manage_encounter is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit manage_encounter? +

Yes. Add a rate_limit block to the manage_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.

How do I block manage_encounter completely? +

Set action: deny in the PolicyLayer policy for manage_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.

What MCP server provides manage_encounter? +

manage_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.