aseprite_run_lua · Aseprite MCP: Risk & Policy

WHAT IT DOES

What aseprite_run_lua does on Aseprite

AI agents invoke aseprite_run_lua to trigger actions in Aseprite. 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.

WHY IT NEEDS A POLICY

Why aseprite_run_lua needs a policy

This is an Execute risk because it allows running arbitrary code (Lua scripts) whose effects depend entirely on the script arguments provided. While Lua scripts in Aseprite are constrained to the application's sandbox, they can still perform destructive operations on sprites (delete layers, overwrite files via export), access file metadata, and trigger complex workflows.

From the tool's definition Tool executes arbitrary Lua scripts via Aseprite's scripting engine ('Execute an inline or file-based Aseprite Lua script'). Aseprite's Lua API provides extensive access to sprite manipulation, file operations, and system interactions.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

aseprite_run_lua Rate-limited

aseprite_run_lua stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "aseprite_run_lua": {
      "limits": [
        {
          "counter": "aseprite_run_lua_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about aseprite_run_lua

What does the aseprite_run_lua tool do? +

Execute an inline or file-based Aseprite Lua script, optionally opening input sprites first. It is categorised as a Execute tool in the Aseprite MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on aseprite_run_lua? +

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

What risk level is aseprite_run_lua? +

aseprite_run_lua is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit aseprite_run_lua? +

Yes. Add a rate_limit block to the aseprite_run_lua 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 aseprite_run_lua completely? +

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

aseprite_run_lua is provided by the Aseprite MCP server (ryan3719/asprite-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.