Medium Risk

telegram-read-stories

Mark stories as seen up to a given story ID (maxId, inclusive).

How to control telegram-read-stories ↓

What telegram-read-stories does on MCP-Telegram

AI agents use telegram-read-stories to create or update resources in MCP-Telegram — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP-Telegram environment.

Medium Risk

Why telegram-read-stories needs a policy

This tool modifies state on Telegram's servers by marking stories as seen, which is a write operation (updating read/seen status). It is reversible in the sense that it doesn't delete content, but it does change persistent state. The blast radius is medium since misuse could mark stories as seen without user intent, affecting privacy (revealing to story posters that the account has viewed their stories).

From the tool's definition Mark stories as seen up to a given story ID (maxId, inclusive)

Documented attack patterns abuse exactly the kind of access telegram-read-stories gives an agent:

How to control telegram-read-stories

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-read-stories:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "telegram-read-stories": {
      "limits": [
        {
          "counter": "telegram-read-stories_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

telegram-read-stories stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register MCP-Telegram — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about telegram-read-stories

What does the telegram-read-stories tool do? +

Mark stories as seen up to a given story ID (maxId, inclusive). It is categorised as a Write tool in the MCP-Telegram MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on telegram-read-stories? +

Register the MCP-Telegram MCP server in PolicyLayer and add a rule for telegram-read-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.

What risk level is telegram-read-stories? +

telegram-read-stories is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit telegram-read-stories? +

Yes. Add a rate_limit block to the telegram-read-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.

How do I block telegram-read-stories completely? +

Set action: deny in the PolicyLayer policy for telegram-read-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.

What MCP server provides telegram-read-stories? +

telegram-read-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.

Enforce policy on every MCP-Telegram tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.