Move a frame to a new position in the animation sequence
AI agents use move_frame 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 operation creates or modifies data in a reversible manner. Moving frames changes the order/structure of animation data without permanent deletion, making it a Write action rather than Destructive. While it could disrupt an animation's intended sequence if misused by an agent (medium severity), the action can be undone by moving the frame back to its original position.
From the tool's definition The tool 'move_frame' modifies the animation sequence by repositioning frames. The description states it moves 'a frame to a new position in the animation sequence,' which is a reversible modification of project structure.
Documented attack patterns abuse exactly the kind of access move_frame 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 move_frame:
{
"version": "1",
"default": "deny",
"tools": {
"move_frame": {
"limits": [
{
"counter": "move_frame_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}move_frame 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.
Move a frame to a new position in the animation sequence. 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 move_frame: 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.
move_frame 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 move_frame 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 move_frame. 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.
move_frame 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.