AI agents call get_nearby_chats to retrieve information from Telegram MCP Complete without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves nearby chats or people based on location data. It performs a read-only operation with no side effects on data, no code execution, no financial implications, and no destructive actions. The low severity reflects minimal risk even if misused—returning location-based chat lists causes no harm beyond potential privacy concerns about data access patterns.
From the tool's definition Tool name 'get_nearby_chats' and description '获取附近的人/群组' (get nearby people/groups) indicate a retrieval operation. The function fetches location-based chat data without modifying, deleting, or executing operations.
Documented attack patterns abuse exactly the kind of access get_nearby_chats gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Telegram MCP Complete, and nothing reaches the server without passing your rules. This is the rule we recommend for get_nearby_chats:
{
"version": "1",
"default": "deny",
"tools": {
"get_nearby_chats": {}
}
}get_nearby_chats 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.
获取附近的人/群组. It is categorised as a Read tool in the Telegram MCP Complete MCP Server, which means it retrieves data without modifying state.
Register the Telegram MCP Complete MCP server in PolicyLayer and add a rule for get_nearby_chats: 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 Complete. Nothing to install.
get_nearby_chats 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_nearby_chats 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_nearby_chats. 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_nearby_chats is provided by the Telegram MCP Complete MCP server (you922/telegram-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Telegram MCP Complete, 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.
153 Telegram MCP Complete tools catalogued and risk-classified — across an index of 43,000+ MCP servers.