AI agents use ghost_create_tag 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 new data (tags) in the Ghost CMS system. Creation is a Write operation—it modifies the system state but remains reversible (tags can be updated or deleted). Severity is medium because unauthorized tag creation could pollute the CMS taxonomy and affect content organization, but it does not directly delete content, execute arbitrary code, or move money. The impact is localized to tag management.
From the tool's definition Tool name 'ghost_create_tag' and description 'Creates a new tag in Ghost CMS' indicate data creation. Tags are metadata that can be modified or deleted later, making this a reversible operation.
Documented attack patterns abuse exactly the kind of access ghost_create_tag 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_create_tag:
{
"version": "1",
"default": "deny",
"tools": {
"ghost_create_tag": {
"limits": [
{
"counter": "ghost_create_tag_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}ghost_create_tag 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.
Creates a new tag in Ghost CMS. 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_create_tag: 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_create_tag 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_create_tag 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_create_tag. 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_create_tag 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.