Get the total number of subscribers to your Substack publication. Useful for tracking growth and understanding your audience size.
AI agents call get_subscriber_count to retrieve information from Substack Mcp Plus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries subscriber count data but does not create, modify, delete, execute code, or commit financial transactions. It is a read-only operation that retrieves metrics about the publication's audience. The blast radius is minimal; misuse would only expose already-public subscription statistics.
From the tool's definition Tool name is 'get_subscriber_count' and description states it 'Get[s] the total number of subscribers' — a pure retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_subscriber_count gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Substack Mcp Plus, and nothing reaches the server without passing your rules. This is the rule we recommend for get_subscriber_count:
{
"version": "1",
"default": "deny",
"tools": {
"get_subscriber_count": {}
}
} get_subscriber_count 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.
Get the total number of subscribers to your Substack publication. Useful for tracking growth and understanding your audience size. It is categorised as a Read tool in the Substack Mcp Plus MCP Server, which means it retrieves data without modifying state.
Register the Substack Mcp Plus MCP server in PolicyLayer and add a rule for get_subscriber_count: 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 Substack Mcp Plus. Nothing to install.
get_subscriber_count 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 get_subscriber_count 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 get_subscriber_count. 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.
get_subscriber_count is provided by the Substack Mcp Plus MCP server (ty13r/substack-mcp-plus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Substack Mcp Plus, 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.
12 Substack Mcp Plus tools catalogued and risk-classified — across an index of 43,000+ MCP servers.