Fetch currently active stories posted by a specific peer (user/channel). Returns compact story metadata (id, date, expireDate, caption, mediaType, counters) with media type className only — no raw media blobs. Use telegram-download-media with the story id if you need media bytes.
AI agents call telegram-get-peer-stories 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 a Read operation—it retrieves and queries story metadata with no side effects. However, severity is high rather than low because: (1) the server operates as a userbot with 'full access to your chats, contacts, and message history' per the server description, meaning this tool can access private stories from any peer the account follows; (2) stories are ephemeral and often contain sensitive content; (3) in an…
From the tool's definition Tool fetches story metadata from a specific peer (user/channel) and returns story id, date, expireDate, caption, mediaType, counters. The description explicitly states 'no raw media blobs' are returned, confirming it retrieves data without modification.
Documented attack patterns abuse exactly the kind of access telegram-get-peer-stories 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-peer-stories:
{
"version": "1",
"default": "deny",
"tools": {
"telegram-get-peer-stories": {}
}
}telegram-get-peer-stories 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.
Fetch currently active stories posted by a specific peer (user/channel). Returns compact story metadata (id, date, expireDate, caption, mediaType, counters) with media type className only — no raw media blobs. Use telegram-download-media with the story id if you need media bytes. 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-peer-stories: 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-peer-stories 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-peer-stories 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-peer-stories. 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-peer-stories 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.