Critical Risk →

delete_project

Delete a project

How to control delete_project ↓

What delete_project does on Piskel MCP Server

AI agents call delete_project to permanently remove resources in Piskel MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete_project needs a policy

This tool permanently removes a project and cannot be undone. While the blast radius is limited to pixel art projects (not production data or financial systems), the destructive nature of deletion and lack of reversibility places it in the Destructive category with high severity. Confidence is high because the name and description leave no ambiguity about the irreversible effect.

From the tool's definition Tool name is 'delete_project' with description 'Delete a project'. The verb 'delete' combined with 'project' indicates irreversible removal of data.

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

How to control delete_project

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

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_project"
  ]
}

delete_project disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_project

What does the delete_project tool do? +

Delete a project. It is categorised as a Destructive tool in the Piskel MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_project? +

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

delete_project is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_project? +

Yes. Add a rate_limit block to the delete_project 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 delete_project completely? +

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

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

Free to start. No card required.

45 Piskel MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.