Per-post analytics for a channel\
AI agents call get_post_insights 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 retrieves and queries post-level analytics information. It performs a read-only data retrieval operation with no ability to modify, delete, or execute actions. The blast radius of misuse is minimal—an agent could at worst access analytics data the authenticated user already has permission to view, with no irreversible consequences or external operations triggered.
From the tool's definition Tool name 'get_post_insights' and description 'Per-post analytics for a channel' indicate retrieval of analytics data with no modification or side effects.
Attacks that exploit this kind of access
Per-post analytics for a channel\. 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_insights: 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_insights 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_insights 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_insights. 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_insights 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 →