Deletes a content type (Admin privileges required).
AI agents call delete_content_type 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.
Deleting a content type is an irreversible operation that removes the schema definition and typically cascades to delete all entries of that type. This is a destructive action with severe blast radius—an AI agent misusing this could eliminate critical data structures from the CMS. The requirement for admin privileges reflects the high-risk nature.
From the tool's definition Tool name is 'delete_content_type' and description states it 'Deletes a content type'. The verb 'deletes' combined with the scope (entire content type, not individual entries) indicates irreversible removal of data structure and potentially all associated…
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access delete_content_type gives an agent:
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_content_type:
{
"version": "1",
"default": "deny",
"hide": [
"delete_content_type"
]
} delete_content_type disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Deletes a content type (Admin privileges required). 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.
Register the Strapi MCP Server MCP server in PolicyLayer and add a rule for delete_content_type: 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.
delete_content_type is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_content_type 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 delete_content_type. 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.
delete_content_type 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.
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.