Resize the canvas of a project. Existing pixels are preserved and positioned at the given anchor point.
AI agents use resize_canvas 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.
Resizing canvas modifies project metadata and pixel positioning but does not delete data (pixels are preserved). This is a reversible Write operation—the user can resize again to undo or revert changes. It does not execute arbitrary operations, destroy data irreversibly, or cause financial impact.
From the tool's definition Tool modifies canvas dimensions and repositions existing pixels ('Existing pixels are preserved and positioned at the given anchor point'), which is a reversible data transformation on the project structure.
Documented attack patterns abuse exactly the kind of access resize_canvas 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 resize_canvas:
{
"version": "1",
"default": "deny",
"tools": {
"resize_canvas": {
"limits": [
{
"counter": "resize_canvas_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}resize_canvas 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.
Resize the canvas of a project. Existing pixels are preserved and positioned at the given anchor point. 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 resize_canvas: 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.
resize_canvas 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 resize_canvas 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 resize_canvas. 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.
resize_canvas 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.