upload_lua_module · Electra One MCP: Risk & Policy

WHAT IT DOES

What upload_lua_module does on Electra One

AI agents use upload_lua_module to create or update resources in Electra One — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Electra One environment.

WHY IT NEEDS A POLICY

Why upload_lua_module needs a policy

Uploading a Lua module to an embedded music device creates or modifies executable code on the device, which is reversible (modules can be overwritten or removed). This is a Write action rather than Execute because the tool itself doesn't run code—it stages code for execution. However, the device context and proximity to execute_lua suggest moderate risk if a malicious module were uploaded.

From the tool's definition Tool named 'upload_lua_module' with no description provided. The name and context (Electra One MK2/Mini widget development) indicate the tool uploads/installs Lua code modules to a device.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

upload_lua_module Rate-limited

upload_lua_module stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "upload_lua_module": {
      "limits": [
        {
          "counter": "upload_lua_module_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Electra One, so you can run agents against it safely.

FAQ

Questions about upload_lua_module

What does the upload_lua_module tool do? +

upload_lua_module. It is categorised as a Write tool in the Electra One MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on upload_lua_module? +

Register the Electra One MCP server in PolicyLayer and add a rule for upload_lua_module: 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 Electra One. Nothing to install.

What risk level is upload_lua_module? +

upload_lua_module is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit upload_lua_module? +

Yes. Add a rate_limit block to the upload_lua_module 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.

How do I block upload_lua_module completely? +

Set action: deny in the PolicyLayer policy for upload_lua_module. 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.

What MCP server provides upload_lua_module? +

upload_lua_module is provided by the Electra One MCP server (roomi-fields/electra-one-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.