List all segments for a publication
AI agents call list_segments to retrieve information from Beehiiv Analytics MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves segment information without creating, modifying, deleting, or executing any operations. It simply lists existing data from the Beehiiv analytics system. The read-only nature of the server and the retrieval-only semantics of the list operation place this firmly in the Read category with low severity.
From the tool's definition Tool name 'list_segments' and description 'List all segments for a publication' indicate a retrieval operation. Server description explicitly states 'read-only access' to analytics data.
Attacks that exploit this kind of access
List all segments for a publication. It is categorised as a Read tool in the Beehiiv Analytics MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Beehiiv Analytics MCP Server MCP server in PolicyLayer and add a rule for list_segments: 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 Beehiiv Analytics MCP Server. Nothing to install.
list_segments 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 list_segments 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 list_segments. 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.
list_segments is provided by the Beehiiv Analytics MCP Server MCP server (ousepachn/beehiivanalyticsmcp). 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 →