ghost_get_post

Get a post by ID or slug.

Server Ghost CMS MCP matveev-pavel/ghost-mcp
Category Read
Risk class Low
Parameters 00 required

What ghost_get_post does on Ghost CMS MCP

AI agents call ghost_get_post to retrieve information from Ghost CMS MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why ghost_get_post needs a policy

This tool retrieves or queries data (a single post by its ID or slug) with no side effects. It does not create, modify, delete, or execute operations. It falls squarely into the Read category with low severity since the worst-case misuse would only expose existing post content.

From the tool's definition Tool name is 'ghost_get_post' and description states 'Get a post by ID or slug' — uses the verb 'Get' which indicates retrieval without modification.

Questions about ghost_get_post

What does the ghost_get_post tool do? +

Get a post by ID or slug. It is categorised as a Read tool in the Ghost CMS MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ghost_get_post? +

Register the Ghost CMS MCP server in PolicyLayer and add a rule for ghost_get_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 CMS MCP. Nothing to install.

What risk level is ghost_get_post? +

ghost_get_post is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit ghost_get_post? +

Yes. Add a rate_limit block to the ghost_get_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.

How do I block ghost_get_post completely? +

Set action: deny in the PolicyLayer policy for ghost_get_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.

What MCP server provides ghost_get_post? +

ghost_get_post 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.