AI agents call get_entities 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 retrieves session entities (likely contacts, groups, channels) from Telegram without creating, modifying, or deleting data. It is a read-only query operation. Severity is medium because exposure of all entities in a session could reveal sensitive information about the user's Telegram contacts and groups, presenting privacy and social engineering risks if misused by an untrusted agent.
From the tool's definition Tool name 'get_entities' with description 'Get all entities in the current session' — a retrieval operation that queries Telegram session data without modification.
Documented attack patterns abuse exactly the kind of access get_entities gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Telegram MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_entities:
{
"version": "1",
"default": "deny",
"tools": {
"get_entities": {}
}
}get_entities 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 all entities in the current session. 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_entities: 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_entities 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_entities 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_entities. 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_entities is provided by the Telegram MCP Server MCP server (prem-research/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 Server, 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.
6 Telegram MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.