ghost_update_page
AI agents use ghost_update_page to create or update resources in Ghost CMS MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ghost CMS MCP environment.
The tool updates page data in Ghost CMS, which is a reversible write operation. While the description is empty, the context of sibling tools and the CMS domain confirm this modifies content. It is Write rather than Destructive because updates are typically reversible (can be reverted or re-edited).
From the tool's definition Tool name 'ghost_update_page' indicates modification of existing page content. Grouped with create/delete tools (ghost_create_page, ghost_delete_page, ghost_get_page, ghost_list_pages) in a CMS management context where updates are reversible modifications.
Attacks that exploit this kind of access
ghost_update_page. It is categorised as a Write tool in the Ghost CMS MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ghost CMS MCP server in PolicyLayer and add a rule for ghost_update_page: 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 CMS MCP. Nothing to install.
ghost_update_page 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_page 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_page. 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_page is provided by the Ghost CMS MCP server (matveev-pavel/ghost-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →