Manage characters and progression. 👤 CHARACTER LIFECYCLE: 1. create - Define character with class/race/stats (auto-provisions equipment) 2. get/update - View or modify properties 3. add_xp/level_up - Advance character progression ⚔️ FOR COMBAT: - Characters need HP, AC, stats for combat particip...
AI agents use character_manage to create or update resources in Rpg — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rpg environment.
The tool creates, modifies, and deletes character records with persistent effects (XP, levels, stats, equipment). While deletions are mentioned, the context indicates they are game entity removals within a reversible game state system (SQLite-backed persistence), not irreversible data destruction like dropping a database.
From the tool's definition Tool performs character creation ('create - Define character'), modification ('update - modify properties'), deletion ('delete'), and progression changes ('add_xp', 'level_up'). These are reversible write operations on game state.
Documented attack patterns abuse exactly the kind of access character_manage gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Rpg, and nothing reaches the server without passing your rules. This is the rule we recommend for character_manage:
{
"version": "1",
"default": "deny",
"tools": {
"character_manage": {
"limits": [
{
"counter": "character_manage_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}character_manage 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.
Free to start. No card required.
Manage characters and progression. 👤 CHARACTER LIFECYCLE: 1. create - Define character with class/race/stats (auto-provisions equipment) 2. get/update - View or modify properties 3. add_xp/level_up - Advance character progression ⚔️ FOR COMBAT: - Characters need HP, AC, stats for combat participation - Use combat_manage to add characters to encounters 📦 EQUIPMENT NOTE: - provisionEquipment: true (default) auto-grants starting equipment - For custom items, create with item_manage first, then use inventory_manage Actions: create, get, update, list, delete, add_xp, get_progression, level_up Aliases: new/add/spawn->create, fetch/find->get, modify/edit->update. It is categorised as a Write tool in the Rpg MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Rpg MCP server in PolicyLayer and add a rule for character_manage: 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 Rpg. Nothing to install.
character_manage 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 character_manage 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 character_manage. 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.
character_manage is provided by the Rpg MCP server (mnehmos/mnehmos.rpg.mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Rpg, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
47 Rpg tools catalogued and risk-classified — across an index of 43,000+ MCP servers.