AI agents call get_word_mentions_by_channels 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 retrieves and queries aggregated statistics about keyword mentions across Telegram channels. It performs a search/analytics operation returning read-only data (mention counts, view counts, and channel breakdowns). There are no side effects, no data modification, no code execution, and no financial impact. The function is informational and non-destructive.
From the tool's definition Tool description specifies 'Break down keyword mentions by the channels that mention it most' with 'mention/view counts' — purely analytical data retrieval with no modification or execution capability.
Attacks that exploit this kind of access
Break down keyword mentions by the channels that mention it most (channel + mention/view counts). 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_word_mentions_by_channels: 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_word_mentions_by_channels 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_word_mentions_by_channels 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_word_mentions_by_channels. 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_word_mentions_by_channels 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 →