Search Telegram Bot API methods by keyword. Returns matching methods with their parameters. Use this to discover available methods before calling them.
AI agents call telegram_find to retrieve information from Telegram Api without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a search operation that retrieves and returns information about available Telegram Bot API methods. It has no side effects—it does not create, modify, delete, execute, or move resources. It is purely informational, enabling discovery of other methods before they are invoked. This is a classic Read category operation.
From the tool's definition Tool description states "Search Telegram Bot API methods by keyword. Returns matching methods with their parameters." The verb "search" and "returns" indicate data retrieval with no side effects.
Documented attack patterns abuse exactly the kind of access telegram_find gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Telegram Api, and nothing reaches the server without passing your rules. This is the rule we recommend for telegram_find:
{
"version": "1",
"default": "deny",
"tools": {
"telegram_find": {}
}
}telegram_find 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.
Search Telegram Bot API methods by keyword. Returns matching methods with their parameters. Use this to discover available methods before calling them. It is categorised as a Read tool in the Telegram Api MCP Server, which means it retrieves data without modifying state.
Register the Telegram Api MCP server in PolicyLayer and add a rule for telegram_find: 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 Api. Nothing to install.
telegram_find 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_find 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_find. 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_find is provided by the Telegram Api MCP server (timoncool/telegram-api-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Telegram Api, 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 Api tools catalogued and risk-classified — across an index of 43,000+ MCP servers.