Swap two colors in a frame (A becomes B, B becomes A). Can operate on all frames/layers.
AI agents use swap_colors to create or update resources in Piskel MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Piskel MCP Server environment.
Swapping colors modifies the pixel art data (Write category), but the change is reversible by performing another swap. This is not destructive deletion/overwrite (which would be Destructive), nor does it execute external code or commands (Execute). Severity is medium because an agent could accidentally corrupt artwork aesthetics, but the effect is easily undone and doesn't affect data outside the art project itself.
From the tool's definition Tool swaps/replaces colors in frames: 'Swap two colors in a frame (A becomes B, B becomes A)'. This modifies pixel data within the artwork, which is reversible (swapping again restores original state).
Documented attack patterns abuse exactly the kind of access swap_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 swap_colors:
{
"version": "1",
"default": "deny",
"tools": {
"swap_colors": {
"limits": [
{
"counter": "swap_colors_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}swap_colors stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Swap two colors in a frame (A becomes B, B becomes A). Can operate on all frames/layers. It is categorised as a Write tool in the Piskel MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Piskel MCP Server MCP server in PolicyLayer and add a rule for swap_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.
swap_colors is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the swap_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 swap_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.
swap_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.