get_palette

THE RISK

Low Risk

Why get_palette needs a policy

This is a straightforward read operation that queries existing palette information. It has no side effects, cannot modify data, and poses minimal security risk even if called inappropriately by an AI agent.

From the tool's definition Tool name is 'get_palette' and description states 'Get palette information and colors' - this retrieves palette data without modifying, creating, or deleting anything.

Documented attack patterns abuse exactly the kind of access get_palette gives an agent:

POLICY

How to control get_palette

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 get_palette:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_palette": {}
  }
}

get_palette is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Piskel MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Piskel MCP Server tools

Destructive delete_project Delete a project Destructive remove_frame Remove a frame from all layers Destructive remove_layer Remove a layer from the project Destructive remove_palette_color Remove a color from a palette Write clear_frame Clear all pixels in a frame Write erase_pixel Erase pixels (set to transparent) Write hue_shift_recolor Recolor sprites by shifting hue. Reads PNGs from an input folder, shifts pixels in a sourc Write add_frame Add a new frame to a layer

All 45 Piskel MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_palette

What does the get_palette tool do? +

Get palette information and colors. It is categorised as a Read tool in the Piskel MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_palette? +

Register the Piskel MCP Server MCP server in PolicyLayer and add a rule for get_palette: 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.

What risk level is get_palette? +

get_palette is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_palette? +

Yes. Add a rate_limit block to the get_palette 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.

How do I block get_palette completely? +

Set action: deny in the PolicyLayer policy for get_palette. 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.

What MCP server provides get_palette? +

get_palette 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.

Enforce policy on every Piskel MCP Server tool call.

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.

CHECK YOUR STACK →