aseprite_command_sequence · Aseprite MCP: Risk & Policy

WHAT IT DOES

What aseprite_command_sequence does on Aseprite

AI agents invoke aseprite_command_sequence 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_command_sequence needs a policy

This tool allows execution of arbitrary Aseprite commands via Lua scripting interface. While focused on pixel art operations, it can trigger any Aseprite command available through the app.command interface, potentially including destructive operations (delete, clear layers/frames) or file system modifications.

From the tool's definition Tool directly executes Aseprite app.command.<CommandId>(params) actions through Lua scripting. The description specifies it 'runs' commands and can perform file operations (opening files, saving sprites), which are external operations with effects determined…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

aseprite_command_sequence Rate-limited

aseprite_command_sequence 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_command_sequence": {
      "limits": [
        {
          "counter": "aseprite_command_sequence_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_command_sequence

What does the aseprite_command_sequence tool do? +

Run Aseprite app.command.<CommandId>(params) actions through Lua, optionally opening files and saving the active sprite. 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_command_sequence? +

Register the Aseprite MCP server in PolicyLayer and add a rule for aseprite_command_sequence: 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_command_sequence? +

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

Can I rate-limit aseprite_command_sequence? +

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

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

aseprite_command_sequence 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.