newsletter_get_stats

Get total newsletter subscriber counts broken down by status (confirmed, pending, unsubscribed).

Server Mcp Bot Crawler merulocal/hellogrowthcrmwebsite_mcp
Category Read
Risk class Low
Parameters 00 required

What newsletter_get_stats does on Mcp Bot Crawler

AI agents call newsletter_get_stats to retrieve information from Mcp Bot Crawler without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why newsletter_get_stats needs a policy

This tool queries and retrieves aggregate data about newsletter subscribers without modifying, creating, or deleting any information. It is a read-only operation similar to fetching statistics or metrics, which falls squarely into the Read category. The data returned is statistical summaries rather than sensitive individual records, and there are no destructive, financial, or code execution implications.

From the tool's definition Tool retrieves newsletter subscriber statistics broken down by status (confirmed, pending, unsubscribed) - a query operation with no side effects or data modification.

Questions about newsletter_get_stats

What does the newsletter_get_stats tool do? +

Get total newsletter subscriber counts broken down by status (confirmed, pending, unsubscribed). It is categorised as a Read tool in the Mcp Bot Crawler MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on newsletter_get_stats? +

Register the Mcp Bot Crawler MCP server in PolicyLayer and add a rule for newsletter_get_stats: 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 Mcp Bot Crawler. Nothing to install.

What risk level is newsletter_get_stats? +

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

Can I rate-limit newsletter_get_stats? +

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

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

newsletter_get_stats is provided by the Mcp Bot Crawler MCP server (merulocal/hellogrowthcrmwebsite_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.