get_participants
AI agents call get_participants to retrieve information from Claudegram without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name strongly suggests querying or listing participants in a chat, which is a read-only operation. Combined with sibling tools showing write/destructive/execute capabilities (ban_participant, block_user, add_contact, etc.), this tool's read-only nature is evident. The empty description reduces confidence slightly, but the semantic meaning of 'get_' prefix is unambiguous as a retrieval operation.
From the tool's definition Tool name 'get_participants' indicates retrieval of participant information from Telegram chats. No parameters or description provided, but naming convention and context within a messaging platform suggest data retrieval without modification.
Attacks that exploit this kind of access
get_participants. It is categorised as a Read tool in the Claudegram MCP Server, which means it retrieves data without modifying state.
Register the Claudegram MCP server in PolicyLayer and add a rule for get_participants: 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 Claudegram. Nothing to install.
get_participants 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_participants 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_participants. 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_participants is provided by the Claudegram MCP server (sanjar-x/claudegram). 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 →