Low Risk

members_browse

members_browse

How to control members_browse ↓

What members_browse does on Ghost MCP Server

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

Low Risk

Why members_browse needs a policy

Browse operations are standard Read category actions that retrieve data for viewing. In a CMS context, browsing members would query the members list without side effects. The Ghost server manages posts, users, and newsletters—browsing members fits the pattern of non-destructive data retrieval.

From the tool's definition Tool name 'members_browse' suggests retrieving or listing member data without modification. The verb 'browse' typically indicates querying/reading operations.

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

How to control members_browse

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

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

members_browse 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 members_browse

What does the members_browse tool do? +

members_browse. 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 members_browse? +

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

What risk level is members_browse? +

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

Can I rate-limit members_browse? +

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

How do I block members_browse completely? +

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

What MCP server provides members_browse? +

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

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.

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