Permanently delete a D&D 5e character by ID or name. Supports batch deletion.
AI agents call delete_character to permanently remove resources in ChatRPG — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes data (character records) and cannot be undone. While the blast radius is limited to game state rather than production systems or financial data, permanent deletion of user-created game content represents a high-severity destructive action. Batch deletion amplifies the risk of accidental or malicious bulk data loss.
From the tool's definition Tool description explicitly states 'Permanently delete' a character; supports 'batch deletion' enabling multi-record removal without recovery.
Attacks that exploit this kind of access
Permanently delete a D&D 5e character by ID or name. Supports batch deletion. It is categorised as a Destructive tool in the ChatRPG MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ChatRPG MCP server in PolicyLayer and add a rule for delete_character: 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.
delete_character is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_character 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 delete_character. 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.
delete_character 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 →