ghost_push_local · Ghost MCP: Risk & Policy

WHAT IT DOES

What ghost_push_local does on Ghost

AI agents use ghost_push_local to create or update resources in Ghost — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ghost environment.

WHY IT NEEDS A POLICY

Why ghost_push_local needs a policy

This tool modifies data (creates new posts or updates existing ones) in a blog CMS, but the changes are reversible—posts can be edited, deleted, or reverted. It does not permanently destroy data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely read data (Read).

From the tool's definition Tool description states 'creates or updates the post' and 'Push a local markdown file to Ghost as a draft'. The verb 'push' combined with 'creates or updates' indicates reversible modification of blog content.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ghost_push_local Rate-limited

ghost_push_local 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.

View as policy code

policy.json

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Ghost, so you can run agents against it safely.

FAQ

Questions about ghost_push_local

What does the ghost_push_local tool do? +

Push a local markdown file to Ghost as a draft. Parses blog format, creates or updates the post. Returns existing tags so Claude can suggest appropriate tags. It is categorised as a Write tool in the Ghost MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on ghost_push_local? +

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

What risk level is ghost_push_local? +

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

Can I rate-limit ghost_push_local? +

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

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

ghost_push_local is provided by the Ghost MCP server (uppinote20/ghost-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.