Critical Risk →

delete_entry

Deletes a specific entry.

How to control delete_entry ↓

What delete_entry does on Strapi MCP Server

AI agents call delete_entry to permanently remove resources in Strapi 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_entry needs a policy

This tool irreversibly removes data from the Strapi CMS. Deletion cannot be undone without a backup restore. While the blast radius is limited to a single entry (not a cascading purge of multiple records), the permanent loss of data and potential cascade to dependent content justify 'high' severity. It does not fall under Financial (no money moved) or Execute (not arbitrary code execution).

From the tool's definition Tool name is 'delete_entry' and description states 'Deletes a specific entry.' The verb 'deletes' and action of removing a specific entry indicate irreversible data destruction.

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

How to control delete_entry

PolicyLayer is an MCP gateway — it sits between your AI agents and Strapi MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_entry:

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

delete_entry 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 Strapi 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_entry

What does the delete_entry tool do? +

Deletes a specific entry. It is categorised as a Destructive tool in the Strapi 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_entry? +

Register the Strapi MCP Server MCP server in PolicyLayer and add a rule for delete_entry: 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 Strapi MCP Server. Nothing to install.

What risk level is delete_entry? +

delete_entry 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_entry? +

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

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

delete_entry is provided by the Strapi MCP Server MCP server (l33tdawg/strapi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Strapi MCP Server tool call.

Start from Strapi 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.

20 Strapi 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.