Manage character rest mechanics (D&D 5e style). ⏰ REST TYPES: - long (8 hours): Full HP restoration, all spell slots restored - short (1 hour): Spend hit dice to heal (roll d8 + CON per die) ⚔️ COMBAT RESTRICTION: Cannot rest while in active combat encounter! ✨ SPELLCASTING: - Full casters: All s...
AI agents use rest_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 or updates character statistics (HP, spell slots, hit dice expenditure) rather than reading data, executing arbitrary operations, or destructing records. While it modifies game state, changes are reversible and constrained to game mechanics.
From the tool's definition Tool performs reversible modifications to character state: 'Full HP restoration, all spell slots restored' (long rest) and 'Spend hit dice to heal' (short rest).
Documented attack patterns abuse exactly the kind of access rest_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 rest_manage:
{
"version": "1",
"default": "deny",
"tools": {
"rest_manage": {
"limits": [
{
"counter": "rest_manage_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}rest_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 character rest mechanics (D&D 5e style). ⏰ REST TYPES: - long (8 hours): Full HP restoration, all spell slots restored - short (1 hour): Spend hit dice to heal (roll d8 + CON per die) ⚔️ COMBAT RESTRICTION: Cannot rest while in active combat encounter! ✨ SPELLCASTING: - Full casters: All spell slots restored on long rest - Warlocks: Pact slots restore on SHORT rest - Concentration spells cleared on long rest Actions: long, short Aliases: long_rest/full→long, short_rest/quick→short. 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 rest_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.
rest_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 rest_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 rest_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.
rest_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.