Manage spell concentration (D&D 5e rules). 🎯 WHEN TO USE: - After damage: check_save (CON save DC = max(10, damage/2)) - After incapacitation/death: check_auto (auto-break) - Before new concentration spell: break (new_spell reason) - Each round: check_duration (for time-limited spells) ⚔️ COMBAT...
AI agents invoke concentration_manage to trigger actions in Rpg. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes game-engine operations (saving throws, auto-breaking concentration, duration checks) that alter the persistent game state in SQLite. It goes beyond mere data retrieval or simple writes — it triggers deterministic mechanical evaluations and cascading state changes (e.g., breaking concentration ends spell effects).
From the tool's definition Manage spell concentration (D&D 5e rules)... check_save, check_auto, break, check_duration — triggers game engine logic, saves, and state transitions
Documented attack patterns abuse exactly the kind of access concentration_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 concentration_manage:
{
"version": "1",
"default": "deny",
"tools": {
"concentration_manage": {
"limits": [
{
"counter": "concentration_manage_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}concentration_manage stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Manage spell concentration (D&D 5e rules). 🎯 WHEN TO USE: - After damage: check_save (CON save DC = max(10, damage/2)) - After incapacitation/death: check_auto (auto-break) - Before new concentration spell: break (new_spell reason) - Each round: check_duration (for time-limited spells) ⚔️ COMBAT INTEGRATION: When a concentrating character takes damage, ALWAYS call check_save! The engine handles the CON save automatically. 🔮 SPELL EXAMPLES (require concentration): Hold Person, Bless, Haste, Hex, Hunter. It is categorised as a Execute tool in the Rpg MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Rpg MCP server in PolicyLayer and add a rule for concentration_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.
concentration_manage is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the concentration_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 concentration_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.
concentration_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.