microcms_get_content

THE RISK

Low Risk

Why microcms_get_content needs a policy

This tool retrieves data from microCMS without modifying, deleting, or executing operations. It has no side effects on the CMS state. The low severity reflects that data retrieval alone poses minimal risk—the blast radius of misuse is limited to unauthorized information disclosure rather than data loss, modification, or financial impact.

From the tool's definition Tool name and description indicate retrieval of a specific content item: 'Get a specific content from microCMS'. The verb 'Get' and the retrieval context match the Read category pattern (get, fetch, retrieve).

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

POLICY

How to control microcms_get_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_get_content:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "microcms_get_content": {}
  }
}

microcms_get_content is read-only, so it stays allowed — but 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.

CAP 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_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_meta Get a specific content with metadata from microCMS Management API. IMPORTANT: Use this too

All 14 microCMS MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about microcms_get_content

What does the microcms_get_content tool do? +

Get a specific content from microCMS. It is categorised as a Read tool in the microCMS MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on microcms_get_content? +

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

microcms_get_content is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit microcms_get_content? +

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

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

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