Search for posts in Ghost CMS by query string with optional status filtering.
AI agents call ghost_search_posts to retrieve information from Ghost MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing posts based on search criteria. It performs a read-only operation with no ability to create, modify, delete, or execute external actions. The only parameters are search query and optional status filters, both of which are safe for filtering results. The blast radius of misuse is minimal—an AI agent could only retrieve unintended post data, not modify or harm content.
From the tool's definition Tool name 'ghost_search_posts' and description 'Search for posts in Ghost CMS by query string with optional status filtering' indicate a search/query operation with no data modification or side effects.
Documented attack patterns abuse exactly the kind of access ghost_search_posts 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_search_posts:
{
"version": "1",
"default": "deny",
"tools": {
"ghost_search_posts": {}
}
}ghost_search_posts is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search for posts in Ghost CMS by query string with optional status filtering. It is categorised as a Read tool in the Ghost MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Ghost MCP Server MCP server in PolicyLayer and add a rule for ghost_search_posts: 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_search_posts is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ghost_search_posts 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_search_posts. 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_search_posts 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.