AI agents call tags_browse 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.
The 'browse' operation pattern in REST conventions and Ghost CMS context typically retrieves or lists resources without modification. Given the sibling tools follow consistent naming and '_browse' tools are read operations, this tool retrieves tag data from Ghost CMS. No capability to create, modify, delete, or execute is indicated.
From the tool's definition Tool name 'tags_browse' suggests browsing/listing tags in Ghost CMS. The '_browse' suffix pattern is consistent with read operations (see sibling tools like 'invites_browse', 'members_browse', 'newsletters_browse' which are query/list operations).
Documented attack patterns abuse exactly the kind of access tags_browse 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 tags_browse:
{
"version": "1",
"default": "deny",
"tools": {
"tags_browse": {}
}
}tags_browse 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.
tags_browse. 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 tags_browse: 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.
tags_browse 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 tags_browse 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 tags_browse. 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.
tags_browse is provided by the Ghost MCP Server MCP server (mfydev/ghost-mcp). 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.
42 Ghost MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.