microcms_patch_content_status

THE RISK

Medium Risk

Why microcms_patch_content_status needs a policy

This tool modifies the publication status of content, which is a reversible state change. It does not delete or destroy data (ruling out Destructive), does not involve financial transactions (ruling out Financial), and does not execute arbitrary code (ruling out Execute).

From the tool's definition Tool name 'microcms_patch_content_status' and description 'Change content publication status in microCMS' indicate modification of existing content state between PUBLISH and DRAFT statuses.

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

POLICY

How to control microcms_patch_content_status

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "microcms_patch_content_status": {
      "limits": [
        {
          "counter": "microcms_patch_content_status_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

microcms_patch_content_status stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

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.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More microCMS MCP Server tools

Destructive microcms_delete_content Delete content from microCMS 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_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 →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about microcms_patch_content_status

What does the microcms_patch_content_status tool do? +

Change content publication status in microCMS (Management API). Can change status between PUBLISH (published) and DRAFT (draft). Note: Only transitions between. It is categorised as a Write tool in the microCMS MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on microcms_patch_content_status? +

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

microcms_patch_content_status is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit microcms_patch_content_status? +

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

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

microcms_patch_content_status 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 →