Get per-post engagement metrics (likes, comments, reach, impressions, saves, shares, plays, clicks, watch time) for a connected social account. Supports Instagram, Facebook, LinkedIn, Google Business Profile, Pinterest, YouTube, and Threads. Returns the most recent posts first. presentation contr...
AI agents call get_post_analytics to retrieve information from Posterly without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves analytics data from social media accounts without any side effects, data modification, or irreversible actions. It is a pure read operation that returns engagement metrics in various formats. The only parameters are for filtering presentation output, not for modifying underlying data.
From the tool's definition Tool performs retrieval of post engagement metrics (likes, comments, reach, impressions, saves, shares, plays, clicks, watch time) with no modification, creation, or deletion of data. Description uses 'Get' and specifies data retrieval only.
Attacks that exploit this kind of access
Get per-post engagement metrics (likes, comments, reach, impressions, saves, shares, plays, clicks, watch time) for a connected social account. Supports Instagram, Facebook, LinkedIn, Google Business Profile, Pinterest, YouTube, and Threads. Returns the most recent posts first. presentation controls output: compact for Telegram/mobile, table for Markdown clients, json for custom chart/card renderers. It is categorised as a Read tool in the Posterly MCP Server, which means it retrieves data without modifying state.
Register the Posterly MCP server in PolicyLayer and add a rule for get_post_analytics: 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 Posterly. Nothing to install.
get_post_analytics 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 get_post_analytics 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 get_post_analytics. 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.
get_post_analytics is provided by the Posterly MCP server (posterly-mcp-server). 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 →