Low Risk

get_list_subscribers_tool

Get subscribers for a specific mailing list.

How to control get_list_subscribers_tool ↓

AI agents call get_list_subscribers_tool to retrieve information from Listmonk MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves subscriber data from a mailing list without modifying, deleting, or executing any operations. It is a straightforward query operation that returns information. The severity is low because exposure of this tool would allow read-only access to subscriber lists—a data enumeration risk, but without capability to modify, delete, or execute changes.

From the tool's definition Tool name 'get_list_subscribers_tool' and description 'Get subscribers for a specific mailing list' indicate a retrieval operation with no side effects.

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

PolicyLayer is an MCP gateway — it sits between your AI agents and Listmonk MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_list_subscribers_tool:

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

get_list_subscribers_tool 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 Listmonk 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.

Go deeper

What does the get_list_subscribers_tool tool do? +

Get subscribers for a specific mailing list. It is categorised as a Read tool in the Listmonk MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_list_subscribers_tool? +

Register the Listmonk MCP Server MCP server in PolicyLayer and add a rule for get_list_subscribers_tool: 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 Listmonk MCP Server. Nothing to install.

What risk level is get_list_subscribers_tool? +

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

Can I rate-limit get_list_subscribers_tool? +

Yes. Add a rate_limit block to the get_list_subscribers_tool 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 get_list_subscribers_tool completely? +

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

get_list_subscribers_tool is provided by the Listmonk MCP Server MCP server (rhnvrm/listmonk-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Listmonk MCP Server tool call.

Deterministic rules across all 29 Listmonk MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

29 Listmonk MCP Server tools catalogued and risk-classified — across an index of 42,500+ 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.