AI agents use manage_condition 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 creates or modifies data (D&D conditions) in a reversible manner. Adding/removing conditions and ticking duration are Write operations—they change game state but are not destructive since conditions can be removed or re-applied. Within the gaming context, misuse could disrupt gameplay balance (e.g., applying unwanted conditions), justifying medium severity.
From the tool's definition Tool performs state modifications (add, remove, tick duration) on game conditions; the verbs 'add' and 'remove' indicate reversible write operations that alter game state.
Attacks that exploit this kind of access
Manage D&D 5e conditions on targets (add, remove, query, tick duration). 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 manage_condition: 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.
manage_condition 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 manage_condition 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 manage_condition. 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.
manage_condition 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 →