Updates an existing post in Ghost CMS. Can update title, content, status, tags, images, and SEO fields. Only the provided fields are changed; omitted fields remain unchanged. Note: tags and authors arrays are fully replaced, not merged with existing values.
AI agents use ghost_update_post to create or update resources in Ghost MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ghost MCP Server environment.
This tool creates or modifies data reversibly. It updates existing posts with new content, metadata, and tags—classic write operations. While the changes persist and affect published content, they are not irreversible (posts can be edited again or reverted manually).
From the tool's definition Tool description states it 'Updates an existing post in Ghost CMS' and can modify 'title, content, status, tags, images, and SEO fields.' The verb 'Updates' and capability to modify multiple content fields clearly indicate a write operation.
Documented attack patterns abuse exactly the kind of access ghost_update_post gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ghost MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for ghost_update_post:
{
"version": "1",
"default": "deny",
"tools": {
"ghost_update_post": {
"limits": [
{
"counter": "ghost_update_post_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}ghost_update_post 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.
Free to start. No card required.
Updates an existing post in Ghost CMS. Can update title, content, status, tags, images, and SEO fields. Only the provided fields are changed; omitted fields remain unchanged. Note: tags and authors arrays are fully replaced, not merged with existing values. It is categorised as a Write tool in the Ghost MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ghost MCP Server MCP server in PolicyLayer and add a rule for ghost_update_post: 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 MCP Server. Nothing to install.
ghost_update_post is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the ghost_update_post 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.
Set action: deny in the PolicyLayer policy for ghost_update_post. 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.
ghost_update_post is provided by the Ghost MCP Server MCP server (jgardner04/ghost-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ghost MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
39 Ghost MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.