AI agents call telegram-get-scheduled 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 tool retrieves/queries existing scheduled messages without modifying, deleting, or executing actions. It is purely informational. While the underlying MCP-Telegram server is powerful (userbot access to personal account, chats, contacts, history), this specific tool only reads data.
From the tool's definition Tool name is 'telegram-get-scheduled' and description states 'List scheduled messages in a Telegram chat' — a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access telegram-get-scheduled 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-scheduled:
{
"version": "1",
"default": "deny",
"tools": {
"telegram-get-scheduled": {}
}
} telegram-get-scheduled 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.
List scheduled messages in a Telegram chat. 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-scheduled: 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-scheduled 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-scheduled 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-scheduled. 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-scheduled 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.