Get a list of all unique colors used in a frame with pixel counts. Useful for palette analysis and color management.
AI agents call get_used_colors to retrieve information from Piskel MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes existing data from a pixel art frame without modifying, creating, deleting, or executing anything. It has no capacity to alter state or cause harm, making it a straightforward Read operation with minimal security risk.
From the tool's definition Tool description states 'Get a list of all unique colors used in a frame' — a retrieval operation with no side effects. The action is explicitly a query ('get_used_colors') that returns data ('with pixel counts') for analysis purposes.
Documented attack patterns abuse exactly the kind of access get_used_colors gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Piskel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_used_colors:
{
"version": "1",
"default": "deny",
"tools": {
"get_used_colors": {}
}
}get_used_colors is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get a list of all unique colors used in a frame with pixel counts. Useful for palette analysis and color management. It is categorised as a Read tool in the Piskel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Piskel MCP Server MCP server in PolicyLayer and add a rule for get_used_colors: 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 Piskel MCP Server. Nothing to install.
get_used_colors 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 get_used_colors 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 get_used_colors. 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.
get_used_colors is provided by the Piskel MCP Server MCP server (yafeiaa/piskel-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Piskel MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
45 Piskel MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.