AI agents call users_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' pattern in the Ghost CMS API context refers to querying or listing resources. No description is provided, but the tool name and consistent naming convention across sibling tools (which retrieve data) strongly indicate this is a read operation that retrieves or lists users without side effects. JWT authentication suggests proper access control is in place.
From the tool's definition Tool name 'users_browse' indicates a browse/list operation. The server description emphasizes 'managing posts, users, and newsletters' and mentions 'JWT authentication for secure access.' Sibling tools like 'members_browse', 'newsletters_browse', and…
Documented attack patterns abuse exactly the kind of access users_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 users_browse:
{
"version": "1",
"default": "deny",
"tools": {
"users_browse": {}
}
}users_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.
users_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 users_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.
users_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 users_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 users_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.
users_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.