Uploads an image and assigns it as the feature image of a post or page (with optional alt text and caption) in one call. Accepts the same imageUrl/imagePath/imageBase64 input modes as ghost_upload_image. Returns the updated resource. If the update fails after the upload, the error response includ...
AI agents use ghost_set_feature_image 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/modifies data (uploads an image and updates a post/page resource with the feature image). It is reversible—a user can delete or change the feature image later. While it writes content to the CMS, it does not delete data or execute arbitrary code.
From the tool's definition Uploads an image and assigns it as the feature image of a post or page...Returns the updated resource. Accepts imageUrl/imagePath/imageBase64 input modes.
Documented attack patterns abuse exactly the kind of access ghost_set_feature_image 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_set_feature_image:
{
"version": "1",
"default": "deny",
"tools": {
"ghost_set_feature_image": {
"limits": [
{
"counter": "ghost_set_feature_image_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}ghost_set_feature_image 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.
Uploads an image and assigns it as the feature image of a post or page (with optional alt text and caption) in one call. Accepts the same imageUrl/imagePath/imageBase64 input modes as ghost_upload_image. Returns the updated resource. If the update fails after the upload, the error response includes the orphaned image URL. 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_set_feature_image: 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_set_feature_image 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_set_feature_image 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_set_feature_image. 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_set_feature_image 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.