List newsletter subscribers with status filter and pagination.
AI agents call newsletter_get_subscribers 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.
This tool retrieves newsletter subscriber information without creating, modifying, or deleting data. It has no side effects beyond querying existing records. While subscriber lists may be sensitive PII, the tool itself performs only read access.
From the tool's definition Tool name 'newsletter_get_subscribers' and description 'List newsletter subscribers with status filter and pagination' indicates data retrieval without modification. Uses list/get verbs typical of read operations with filtering and pagination parameters.
Attacks that exploit this kind of access
List newsletter subscribers with status filter and pagination. It is categorised as a Read tool in the Mcp Bot Crawler MCP Server, which means it retrieves data without modifying state.
Register the Mcp Bot Crawler MCP server in PolicyLayer and add a rule for newsletter_get_subscribers: 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.
newsletter_get_subscribers 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 newsletter_get_subscribers 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 newsletter_get_subscribers. 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.
newsletter_get_subscribers 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.
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 →