Get high-level stats for a channel — currently exposes the number of posts Viraly has scheduled or published for that channel. For per-platform metrics like followers, reach, engagement, or impressions, use get_post_insights (per-post breakdown) or trigger_analytics_sync followed by get_post_anal...
AI agents call get_channel_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 queries and retrieves analytics data about scheduled or published posts on a channel. It has no side effects, does not modify data, does not execute arbitrary operations, and does not involve financial transactions. It is a straightforward read operation returning statistics.
From the tool's definition Tool name 'get_channel_analytics' and description 'Get high-level stats for a channel' — retrieves metrics (number of posts scheduled/published) without modification or side effects. Directs users to other tools for detailed analytics.
Attacks that exploit this kind of access
Get high-level stats for a channel — currently exposes the number of posts Viraly has scheduled or published for that channel. For per-platform metrics like followers, reach, engagement, or impressions, use get_post_insights (per-post breakdown) or trigger_analytics_sync followed by get_post_analytics on individual posts. 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_channel_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_channel_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_channel_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_channel_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_channel_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 →