AI agents invoke execute_luau to trigger actions in Melo. 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 allows execution of arbitrary code in the Roblox Studio environment. An AI agent with access to this could execute malicious scripts, manipulate game objects, exfiltrate data from projects, corrupt game logic, or cause widespread damage within Studio. The 'arbitrary' qualifier means there are no restrictions on what code can be run.
From the tool's definition Tool description explicitly states 'Run arbitrary Luau code directly in Studio'. The name 'execute_luau' combined with 'arbitrary code' clearly indicates dynamic code execution capability.
Attacks that exploit this kind of access
Run arbitrary Luau code directly in Studio. It is categorised as a Execute tool in the Melo MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Melo MCP server in PolicyLayer and add a rule for execute_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 Melo. Nothing to install.
execute_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 execute_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 execute_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.
execute_luau is provided by the Melo MCP server (yannyhl/linkedsword-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 →