AI agents invoke execute_action 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 runs combat actions that modify game state (attack outcomes, position changes, resource consumption). While scoped to a game context with limited real-world impact, it executes commands whose effects depend on arguments (which action, target, parameters) and cannot be trivially reversed mid-encounter.
From the tool's definition Tool name 'execute_action' and description 'Execute a combat action in an encounter (attack, dash, disengage, dodge, etc.)' directly indicate execution of game state-altering operations.
Attacks that exploit this kind of access
Execute a combat action in an encounter (attack, dash, disengage, dodge, etc.). Phase 1 supports attack and dash actions. 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 execute_action: 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.
execute_action 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 execute_action 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 execute_action. 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.
execute_action 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 →