Flip a frame horizontally (mirror left-right). Supports applying to all frames.
AI agents use flip_horizontal 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.
This tool modifies existing pixel art data (frames) by applying a geometric transformation. While reversible (flipping twice returns the original state), it constitutes a Write operation because it alters the project's visual content.
From the tool's definition flip_horizontal modifies frame data by transforming pixel positions horizontally. The description states it will 'flip a frame horizontally' and 'supports applying to all frames', indicating direct modification of project state.
Documented attack patterns abuse exactly the kind of access flip_horizontal 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 flip_horizontal:
{
"version": "1",
"default": "deny",
"tools": {
"flip_horizontal": {
"limits": [
{
"counter": "flip_horizontal_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} flip_horizontal 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.
Flip a frame horizontally (mirror left-right). Supports applying to all frames. 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 flip_horizontal: 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.
flip_horizontal 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 flip_horizontal 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 flip_horizontal. 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.
flip_horizontal 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.