Manage party composition. Operations: add (add character to party with optional role), remove (remove character from party), list (show party roster), get (get party member details), set_role (assign role to party member), clear (remove all members). Roles: leader, scout, healer, tank, support, d...
AI agents use manage_party 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 managing party membership and roles. While 'remove' and 'clear' delete party assignments, they are reversible through 'add' operations and do not permanently destroy character entities. The primary operations (add, set_role) are write-class modifications.
From the tool's definition The tool description explicitly lists operations including 'add', 'remove', 'set_role', and 'clear', which create, modify, and reversibly delete party compositions.
Attacks that exploit this kind of access
Manage party composition. Operations: add (add character to party with optional role), remove (remove character from party), list (show party roster), get (get party member details), set_role (assign role to party member), clear (remove all members). Roles: leader, scout, healer, tank, support, damage, utility, other. 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_party: 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_party 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_party 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_party. 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_party 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 →