get_posts_summary_stats

Get aggregate statistics for all posts in a publication

Server Beehiiv Analytics MCP Server ousepachn/beehiivanalyticsmcp
Category Read
Risk class Low
Parameters 00 required

What get_posts_summary_stats does on Beehiiv Analytics MCP Server

AI agents call get_posts_summary_stats 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.

Why get_posts_summary_stats needs a policy

This tool retrieves and queries existing analytics statistics without any side effects. It matches the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch).' The read-only constraint on the entire server and the query nature of aggregate statistics retrieval confirm low risk.

From the tool's definition Tool name 'get_posts_summary_stats' and description 'Get aggregate statistics for all posts in a publication' indicate data retrieval only. Server description explicitly states 'read-only access' to analytics data.

Questions about get_posts_summary_stats

What does the get_posts_summary_stats tool do? +

Get aggregate statistics for all posts in 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.

How do I enforce a policy on get_posts_summary_stats? +

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

What risk level is get_posts_summary_stats? +

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

Can I rate-limit get_posts_summary_stats? +

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

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

get_posts_summary_stats 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.

// 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.