List viewers of one of YOUR stories (stories.GetStoryViewsList). Returns per-viewer entries (user id, view date, their reaction emoji if any), plus totals (viewsCount, forwardsCount, reactionsCount) and nextOffset for pagination. Pass your own user id (numeric) or @username as the peer — this onl...
AI agents call telegram-get-story-views 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 queries and retrieves metadata about story viewers without modifying, deleting, or executing any actions. The severity is low because it only exposes information already available to the story owner through the Telegram app's viewer list feature, and the blast radius of misuse is minimal — an AI could retrieve story metrics without causing harm, unintended consequences, or affecting other users' data.
From the tool's definition The tool 'telegram-get-story-views' retrieves a list of viewers for the user's own stories, returning viewer IDs, view dates, reactions, and aggregated counts.
Documented attack patterns abuse exactly the kind of access telegram-get-story-views 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-story-views:
{
"version": "1",
"default": "deny",
"tools": {
"telegram-get-story-views": {}
}
}telegram-get-story-views 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 viewers of one of YOUR stories (stories.GetStoryViewsList). Returns per-viewer entries (user id, view date, their reaction emoji if any), plus totals (viewsCount, forwardsCount, reactionsCount) and nextOffset for pagination. Pass your own user id (numeric) or @username as the peer — this only works for stories you posted. Some accounts (non-Premium, old stories) may not get a full viewer list — a Premium hint is surfaced on typical errors. 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-story-views: 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-story-views 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-story-views 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-story-views. 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-story-views 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.