AI agents call get_channel_posts to retrieve information from Tgstat 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 historical post data and metrics from a Telegram channel. It has no side effects, does not modify data, execute commands, or trigger external operations. The optional date range and pagination parameters are filtering/navigation options for the read operation. Blast radius if misused is minimal—data exposure of public Telegram channel analytics at worst.
From the tool's definition Tool description states 'Get recent posts of a channel with view metrics' - retrieves/queries data with no modification. The verb 'Get' and lack of any create/update/delete/execute language confirms read-only retrieval.
Attacks that exploit this kind of access
Get recent posts of a channel with view metrics. Supports an optional date range and pagination. It is categorised as a Read tool in the Tgstat MCP Server, which means it retrieves data without modifying state.
Register the Tgstat MCP server in PolicyLayer and add a rule for get_channel_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 Tgstat. Nothing to install.
get_channel_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 get_channel_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 get_channel_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.
get_channel_posts is provided by the Tgstat MCP server (theyahia/tgstat-mcp). 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 →