AI agents call aseprite_list_commands to retrieve information from Aseprite without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns static metadata about available Aseprite commands without executing any of those commands, modifying files, or triggering side effects. It is purely informational, analogous to querying documentation or viewing a command reference. This falls squarely into the Read category with low severity due to minimal blast radius if misused.
From the tool's definition The tool 'aseprite_list_commands' lists Aseprite command IDs from the upstream commands_list.h file. The name and description explicitly indicate a retrieval/query operation ('list') with no modification or execution capability.
Attacks that exploit this kind of access
List Aseprite command IDs known from the upstream commands_list.h. It is categorised as a Read tool in the Aseprite MCP Server, which means it retrieves data without modifying state.
Register the Aseprite MCP server in PolicyLayer and add a rule for aseprite_list_commands: 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.
aseprite_list_commands is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the aseprite_list_commands 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 aseprite_list_commands. 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.
aseprite_list_commands 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.
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 →