Get the number of members in a chat.
AI agents call get_chat_member_count to retrieve information from Telegram Mcp Kit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about a chat (member count) with no side effects. It is a read-only information query operation consistent with the Telegram Bot API's getChat or getChatMembersCount endpoints. Misuse would have minimal impact—an agent could only gather information about chat sizes, not modify or access sensitive data beyond what is already visible.
From the tool's definition Tool name 'get_chat_member_count' and description 'Get the number of members in a chat' indicate a query operation that retrieves information without modifying state.
Attacks that exploit this kind of access
Get the number of members in a chat. It is categorised as a Read tool in the Telegram Mcp Kit MCP Server, which means it retrieves data without modifying state.
Register the Telegram Mcp Kit MCP server in PolicyLayer and add a rule for get_chat_member_count: 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 Telegram Mcp Kit. Nothing to install.
get_chat_member_count 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_chat_member_count 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_chat_member_count. 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_chat_member_count is provided by the Telegram Mcp Kit MCP server (quoctang/telegram-mcp-kit). 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 →