AI agents invoke roll_check 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 randomized dice-roll computation to produce game results. It doesn't read stored data, write/modify persistent data, or perform destructive/financial actions. It falls under Execute because it triggers an external operation (dice roll resolution) whose output depends on arguments like check type and modifiers.
From the tool's definition 'Roll D&D 5e checks including skill checks, ability checks, saving throws, attack rolls, and initiative' — triggers a dice-rolling computation/operation
Attacks that exploit this kind of access
Roll D&D 5e checks including skill checks, ability checks, saving throws, attack rolls, and initiative. 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_check: 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_check 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_check 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_check. 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_check 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 →