Retrieves a list of members (subscribers) from Ghost CMS with optional filtering, pagination, and includes.
AI agents call ghost_get_members 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.
This tool only queries and returns member data without side effects. It matches the Read category definition: retrieves or queries data with no side effects. The severity is low because exposure of subscriber lists, while sensitive, does not enable destructive or financial actions on its own. Confidence is high given the explicit 'Retrieves' language in the description.
From the tool's definition Tool name 'ghost_get_members' and description 'Retrieves a list of members (subscribers)' indicate data retrieval with 'optional filtering, pagination, and includes' — no modification or deletion of data.
Documented attack patterns abuse exactly the kind of access ghost_get_members 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 ghost_get_members:
{
"version": "1",
"default": "deny",
"tools": {
"ghost_get_members": {}
}
}ghost_get_members 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.
Retrieves a list of members (subscribers) from Ghost CMS with optional filtering, pagination, and includes. 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 ghost_get_members: 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.
ghost_get_members 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_get_members 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_get_members. 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_get_members 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.
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.