AI agents invoke run_luau to trigger actions in Dex. 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 arbitrary Luau code in a Roblox client without apparent restrictions or sandboxing. While not permanently destructive by itself, arbitrary code execution in a gaming context represents critical risk: it can call game APIs to modify world state, trigger exploits, exfiltrate sensitive data, or perform actions on behalf of the user.
From the tool's definition Tool description explicitly states 'Execute arbitrary Luau in the Roblox client' and is labeled a 'Power tool'. The sibling tools (fire_remote, invoke_remote, get_properties, get_root) combined with this tool enable full control over a Roblox instance.
Attacks that exploit this kind of access
Execute arbitrary Luau in the Roblox client and return captured output plus a best-effort serialized return value. Power tool. It is categorised as a Execute tool in the Dex MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Dex MCP server in PolicyLayer and add a rule for run_luau: 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 Dex. Nothing to install.
run_luau 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 run_luau 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 run_luau. 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.
run_luau is provided by the Dex MCP server (sanztheo/dex-mcp). 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 →