Get incoming messages from non-contacts (contact requests). Shows who messaged you without being in your contacts, with message preview
AI agents call telegram-get-contact-requests to retrieve information from MCP-Telegram without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is fundamentally a read operation that queries and retrieves data (contact requests and message previews). However, severity is high because the MCP server operates as a userbot with full access to personal Telegram accounts, chats, contacts, and message history.
From the tool's definition Tool explicitly retrieves incoming messages and displays message previews from non-contacts; described as 'Get incoming messages' and 'Shows who messaged you'; no modification, deletion, or execution mentioned.
Documented attack patterns abuse exactly the kind of access telegram-get-contact-requests gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-Telegram, and nothing reaches the server without passing your rules. This is the rule we recommend for telegram-get-contact-requests:
{
"version": "1",
"default": "deny",
"tools": {
"telegram-get-contact-requests": {}
}
} telegram-get-contact-requests is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get incoming messages from non-contacts (contact requests). Shows who messaged you without being in your contacts, with message preview. It is categorised as a Read tool in the MCP-Telegram MCP Server, which means it retrieves data without modifying state.
Register the MCP-Telegram MCP server in PolicyLayer and add a rule for telegram-get-contact-requests: 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 MCP-Telegram. Nothing to install.
telegram-get-contact-requests 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 telegram-get-contact-requests 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 telegram-get-contact-requests. 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.
telegram-get-contact-requests is provided by the MCP-Telegram MCP server (mcp-telegram/mcp-telegram). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP-Telegram, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
181 MCP-Telegram tools catalogued and risk-classified — across an index of 43,000+ MCP servers.