Move a character to a different location
AI agents use move_character to create or update resources in DMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DMCP environment.
The tool creates or modifies game state reversibly by updating a character's location. This is a Write operation rather than Read (retrieves data), Execute (triggers external code/commands), Destructive (permanent deletion), or Financial. The context of a dungeon master RPG server confirms this is internal game state manipulation with no side effects beyond the game itself.
From the tool's definition Tool description states 'Move a character to a different location' - this modifies character state (position/location) within the game world, which is a reversible change to game data.
Documented attack patterns abuse exactly the kind of access move_character gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for move_character:
{
"version": "1",
"default": "deny",
"tools": {
"move_character": {
"limits": [
{
"counter": "move_character_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}move_character 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 different location. It is categorised as a Write tool in the DMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the D MCP server in PolicyLayer and add a rule for move_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 DMCP. Nothing to install.
move_character 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 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. 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 is provided by the D MCP server (shawnrushefsky/dmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from DMCP, 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.
204 DMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.