aseprite_cli · Aseprite MCP: Risk & Policy

WHAT IT DOES

What aseprite_cli does on Aseprite

AI agents invoke aseprite_cli 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_cli needs a policy

The tool executes arbitrary CLI commands in Aseprite's native interface, which can trigger complex operations including file I/O, script execution, and visual transformations.

From the tool's definition Tool description states 'Run raw Aseprite CLI arguments' and 'any native capability not covered by a higher-level tool.' This provides direct execution of arbitrary Aseprite CLI commands without constraints.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

aseprite_cli Rate-limited

aseprite_cli 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_cli": {
      "limits": [
        {
          "counter": "aseprite_cli_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_cli

What does the aseprite_cli tool do? +

Run raw Aseprite CLI arguments. Use for any native capability not covered by a higher-level tool. 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_cli? +

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

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

Can I rate-limit aseprite_cli? +

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

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

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