Get engagement analytics (likes, comments, shares, reach, impressions) for a single published post. Returns null metrics if the post has not been published yet or analytics have not synced.
AI agents call get_post_analytics to retrieve information from Viraly MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns analytics data without creating, modifying, deleting, or executing any operations. It has no capability to change state, trigger external actions, or affect financial systems. The worst-case misuse scenario—an agent repeatedly querying analytics—has minimal blast radius.
From the tool's definition Tool name 'get_post_analytics' and description explicitly states it retrieves engagement metrics (likes, comments, shares, reach, impressions) with no modification or side effects.
Attacks that exploit this kind of access
Get engagement analytics (likes, comments, shares, reach, impressions) for a single published post. Returns null metrics if the post has not been published yet or analytics have not synced. It is categorised as a Read tool in the Viraly MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Viraly MCP Server 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 Viraly MCP Server. 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 Viraly MCP Server MCP server (viraly-io/viraly-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 →