List posts from a publication with various filters
AI agents call list_posts 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/queries posts from a Beehiiv publication with filters applied. It has no side effects—it does not create, modify, delete, or execute anything. The server is explicitly described as providing 'read-only access' to analytics data. Blast radius is minimal; misuse would only expose existing posts the user already has access to.
From the tool's definition Tool name 'list_posts' and server description emphasizing 'read-only access' and 'retrieve' data. No modification, deletion, or execution capabilities mentioned. Filtering is a standard read operation.
Attacks that exploit this kind of access
List posts from a publication with various filters. 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_posts: 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_posts 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_posts 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_posts. 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_posts 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 →