AI agents use set_fps 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 project settings by adjusting the FPS parameter, which is a write operation. It does not create or delete data (Write rather than Read or Destructive), does not execute arbitrary code or external commands (not Execute), and does not involve financial transactions (not Financial). The change is reversible—FPS can be adjusted again to any value.
From the tool's definition "Set the animation frames per second for a project" — modifies animation metadata (FPS) of a project, a reversible configuration change.
Documented attack patterns abuse exactly the kind of access set_fps 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 set_fps:
{
"version": "1",
"default": "deny",
"tools": {
"set_fps": {
"limits": [
{
"counter": "set_fps_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_fps 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.
Set the animation frames per second for a project. 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 set_fps: 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.
set_fps 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 set_fps 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 set_fps. 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.
set_fps 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.