Ghost CMS MCP

17 tools. 11 can modify or destroy data without limits.

3 destructive tools with no built-in limits. Policy required.

Last updated:

11 can modify or destroy data
6 read-only
17 tools total

Community server · catalogue entry verified 02/07/2026

How to control Ghost CMS MCP ↓

What Ghost CMS MCP exposes to your agents

Read (6) Write / Execute (8) Destructive / Financial (3)
Critical Risk

The most dangerous Ghost CMS MCP tools

11 of Ghost CMS MCP's 17 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control Ghost CMS MCP

PolicyLayer is an MCP gateway — it sits between your AI agents and Ghost CMS MCP, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations
{
  "ghost_delete_page": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
{
  "ghost_create_page": {
    "limits": [
      {
        "counter": "ghost_create_page_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "ghost_get_page": {
    "limits": [
      {
        "counter": "ghost_get_page_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register Ghost CMS MCP — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON GHOST CMS →

Instant setup, no code required.

All 17 Ghost CMS MCP tools

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Questions about Ghost CMS MCP

Can an AI agent delete data through the Ghost CMS MCP server? +

Yes. The Ghost CMS MCP server exposes 3 destructive tools including ghost_delete_page, ghost_delete_post, ghost_delete_tag. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Ghost CMS MCP? +

The Ghost CMS MCP server has 8 write tools including ghost_create_page, ghost_create_post, ghost_create_tag. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Ghost CMS MCP.

How many tools does the Ghost CMS MCP server expose? +

17 tools across 3 categories: Destructive, Read, Write. 6 are read-only. 11 can modify, create, or delete data.

How do I enforce a policy on Ghost CMS MCP? +

Register the Ghost CMS MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Ghost CMS MCP tool call.

Deterministic rules across all 17 Ghost CMS MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Instant setup, no code required.

17 Ghost CMS MCP 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.