This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/ghost-list-tags.md
What ghost_list_tags does on UnClick
AI agents call ghost_list_tags to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Tags to return (max 100, default 50) |
site_url | string | Yes | Ghost site URL |
content_key | string | Yes | Ghost Content API key |
Parameters from the server's own tool schema.
Why ghost_list_tags is rated Low
This is a read-only operation that retrieves tag information from a Ghost (blogging platform) instance. It has no side effects, does not modify data, and poses minimal risk if misused by an AI agent. The worst outcome would be retrieving tag information the agent shouldn't have access to, which is a low-severity information disclosure risk.
From the tool's definition Tool name 'ghost_list_tags' and description 'List Ghost tags' indicate a retrieval operation that queries and returns a list of existing tags without modifying or deleting data.
Attacks that exploit this kind of access
The rule that runs ghost_list_tags safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ghost_list_tags, this is the rule to start with:
ghost_list_tags is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every ghost_list_tags call is checked against it from then on.
Questions about ghost_list_tags
List Ghost tags. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
ghost_list_tags accepts 3 parameters: limit, site_url, content_key. Required: site_url, content_key. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for ghost_list_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 UnClick. Nothing to install.
ghost_list_tags 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_list_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.
Set action: deny in the PolicyLayer policy for ghost_list_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.
ghost_list_tags is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue