AI agents call search_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 queries a database of Telegram channels and returns results based on search criteria. It has no side effects, cannot modify data, execute commands, or cause irreversible changes. The optional filters (category, language, country, type) are search parameters that refine the read operation.
From the tool's definition Tool performs 'Search Telegram channels by query' and 'Returns curated channel cards' - pure data retrieval with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Search Telegram channels by query, with optional category / language / country / type filters. Returns curated channel cards. 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 search_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.
search_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 search_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 search_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.
search_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 →