Low Risk

ghost_get_tags

Retrieves a list of tags from Ghost CMS with pagination, filtering, sorting, and relation inclusion. Supports filtering by name, slug, visibility, or custom NQL filter expressions.

How to control ghost_get_tags ↓

What ghost_get_tags does on Ghost MCP Server

AI agents call ghost_get_tags 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.

Low Risk

Why ghost_get_tags needs a policy

This tool queries and retrieves data from Ghost CMS without side effects. It supports read-only operations like filtering and sorting existing tags, but does not create, modify, delete, or execute any operations. It falls squarely into the Read category with low severity due to the absence of any destructive or executable capability.

From the tool's definition Tool description states 'Retrieves a list of tags' with support for 'pagination, filtering, sorting, and relation inclusion'. No modification, deletion, or execution of external operations is mentioned.

Documented attack patterns abuse exactly the kind of access ghost_get_tags gives an agent:

How to control ghost_get_tags

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_get_tags:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "ghost_get_tags": {}
  }
}

ghost_get_tags is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Ghost MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about ghost_get_tags

What does the ghost_get_tags tool do? +

Retrieves a list of tags from Ghost CMS with pagination, filtering, sorting, and relation inclusion. Supports filtering by name, slug, visibility, or custom NQL filter expressions. It is categorised as a Read tool in the Ghost MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ghost_get_tags? +

Register the Ghost MCP Server MCP server in PolicyLayer and add a rule for ghost_get_tags: 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.

What risk level is ghost_get_tags? +

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

Can I rate-limit ghost_get_tags? +

Yes. Add a rate_limit block to the ghost_get_tags 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_tags completely? +

Set action: deny in the PolicyLayer policy for ghost_get_tags. 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_tags? +

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

Enforce policy on every Ghost MCP Server tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.