get_telegram_response
AI agents call get_telegram_response to retrieve information from Telegram MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to retrieve or fetch responses from Telegram users in a human-in-the-loop workflow. Fetching messages is a read operation with minimal risk. No side effects, destructive actions, or state changes occur. Confidence is moderate (0.75) rather than high because the description is empty, leaving some ambiguity about implementation details.
From the tool's definition Tool name 'get_telegram_response' and sibling tools 'ask_human', 'list_telegram_messages', 'send_telegram_notification' indicate this retrieves responses/messages from Telegram.
Attacks that exploit this kind of access
get_telegram_response. It is categorised as a Read tool in the Telegram MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Telegram MCP Server MCP server in PolicyLayer and add a rule for get_telegram_response: 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 Server. Nothing to install.
get_telegram_response 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_telegram_response 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_telegram_response. 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_telegram_response is provided by the Telegram MCP Server MCP server (stoypenny/mcp-kilo-telegram). 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 →