Roll a death saving throw for a character at 0 HP. D&D 5e rules: 10+ success, 9- failure, nat 1 = 2 failures, nat 20 = revive at 1 HP. 3 successes = stable (unconscious but not dying), 3 failures = death. Supports modifiers from spells like Bless and roll modes (advantage/disadvantage). Returns A...
AI agents invoke roll_death_save to trigger actions in ChatRPG. 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 a dice roll simulation and applies game logic (D&D 5e death save rules) to produce a result. It triggers computation and state evaluation (tracking successes/failures, determining death or stabilization) rather than simply reading stored data or writing a persistent record. It is scoped entirely to a fictional RPG context, so blast radius is low even if misused.
From the tool's definition Roll a death saving throw... Returns ASCII-formatted death save result with visual tracker
Attacks that exploit this kind of access
Roll a death saving throw for a character at 0 HP. D&D 5e rules: 10+ success, 9- failure, nat 1 = 2 failures, nat 20 = revive at 1 HP. 3 successes = stable (unconscious but not dying), 3 failures = death. Supports modifiers from spells like Bless and roll modes (advantage/disadvantage). Returns ASCII-formatted death save result with visual tracker. It is categorised as a Execute tool in the ChatRPG MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ChatRPG MCP server in PolicyLayer and add a rule for roll_death_save: 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 ChatRPG. Nothing to install.
roll_death_save 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 roll_death_save 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 roll_death_save. 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.
roll_death_save is provided by the ChatRPG MCP server (mnehmos/mnehmos.chatrpg.game). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →