Import a PNG image into a specific layer and frame. Accepts base64-encoded PNG data OR a file path. The image will be loaded pixel-by-pixel, preserving transparency. If the image dimensions differ from the project, it will be cropped or padded.
AI agents use import_png 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 creates or modifies pixel art data within a project layer, which is a reversible write operation. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), or cause financial impact.
From the tool's definition The tool description states it will 'Import a PNG image into a specific layer and frame' and 'load pixel-by-pixel', which modifies project data by adding/replacing image content on a layer.
Documented attack patterns abuse exactly the kind of access import_png 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 import_png:
{
"version": "1",
"default": "deny",
"tools": {
"import_png": {
"limits": [
{
"counter": "import_png_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}import_png 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.
Import a PNG image into a specific layer and frame. Accepts base64-encoded PNG data OR a file path. The image will be loaded pixel-by-pixel, preserving transparency. If the image dimensions differ from the project, it will be cropped or padded. 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 import_png: 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.
import_png 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 import_png 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 import_png. 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.
import_png 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.