microcms_delete_content

THE RISK

Critical Risk

Why microcms_delete_content needs a policy

This tool performs an irreversible deletion operation on content within a CMS system. Deletion cannot be undone without external backups or recovery mechanisms. The blast radius is critical because an AI agent given misuse control could permanently remove published content, customer data, or important records from the production CMS.

From the tool's definition Tool name is 'microcms_delete_content' and description states 'Delete content from microCMS'. The word 'Delete' explicitly indicates irreversible removal of data.

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

POLICY

How to control microcms_delete_content

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

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "microcms_delete_content"
  ]
}

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

Create a free account and register microCMS 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.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More microCMS MCP Server tools

Destructive microcms_delete_media Delete media files from microCMS (Management API). Supports deletion of both images and fi Write microcms_patch_content_created_by Change content creator in microCMS (Management API). Updates the createdBy field of a cont Write microcms_patch_content_status Change content publication status in microCMS (Management API). Can change status between Write microcms_upload_media Upload media files to microCMS using JS SDK (Management API). Supports two methods: 1) Upl Read microcms_get_api_info Get API schema information from microCMS Management API. In relation and relationList fiel Read microcms_get_api_list Get list of all available APIs (endpoints) from microCMS Management API. Returns API name, Read microcms_get_content Get a specific content from microCMS Read microcms_get_content_meta Get a specific content with metadata from microCMS Management API. IMPORTANT: Use this too

All 14 microCMS MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in microCMS MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about microcms_delete_content

What does the microcms_delete_content tool do? +

Delete content from microCMS. It is categorised as a Destructive tool in the microCMS 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 microcms_delete_content? +

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

What risk level is microcms_delete_content? +

microcms_delete_content 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 microcms_delete_content? +

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

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

microcms_delete_content is provided by the microCMS MCP Server MCP server (microcmsio/microcms-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 microCMS MCP Server tool call.

Start from microCMS 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 →