Edit an existing story: replace media, update caption (
AI agents use telegram-edit-story 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.
This tool modifies story content reversibly. It updates metadata (captions) and media attachments on existing stories, which is a Write operation. Severity is medium because misuse could deface or alter the user's public-facing story content, but the action is reversible (stories can be edited again or deleted).
From the tool's definition Tool description states 'Edit an existing story: replace media, update caption' — modifying existing content (caption/media) without deletion.
Documented attack patterns abuse exactly the kind of access telegram-edit-story 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-edit-story:
{
"version": "1",
"default": "deny",
"tools": {
"telegram-edit-story": {
"limits": [
{
"counter": "telegram-edit-story_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} telegram-edit-story 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.
Free to start. No card required.
Edit an existing story: replace media, update caption (. 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.
Register the MCP-Telegram MCP server in PolicyLayer and add a rule for telegram-edit-story: 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-edit-story is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the telegram-edit-story 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-edit-story. 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-edit-story 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.