Move a character to a room and increment its visit count.
AI agents use move_character_to_room 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.
This tool modifies game state by updating a character's location and visit count, which are persistent changes stored in the SQLite backend. However, these changes are fully reversible (a character can be moved elsewhere, counters can be reset), and the blast radius is confined to game mechanics—no financial, destructive, or external system impact.
From the tool's definition Tool name 'move_character_to_room' and description 'Move a character to a room and increment its visit count' indicate state modification (character position and visit counter) that is reversible within the game simulation.
Documented attack patterns abuse exactly the kind of access move_character_to_room 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 move_character_to_room:
{
"version": "1",
"default": "deny",
"tools": {
"move_character_to_room": {
"limits": [
{
"counter": "move_character_to_room_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}move_character_to_room 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.
Move a character to a room and increment its visit count. 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 move_character_to_room: 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.
move_character_to_room 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 move_character_to_room 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 move_character_to_room. 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.
move_character_to_room 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.