Report a story via the multi-step option flow. First call with option:
AI agents invoke telegram-report-story to trigger actions in MCP-Telegram. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Reporting a story submits a report to Telegram's moderation/platform systems, which is an external operation with real-world effects (potentially leading to content removal or account action). It is not a simple read, nor does it directly delete data or move money.
From the tool's definition 'Report a story via the multi-step option flow' — triggers an external reporting action on Telegram's platform
Documented attack patterns abuse exactly the kind of access telegram-report-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-report-story:
{
"version": "1",
"default": "deny",
"tools": {
"telegram-report-story": {
"limits": [
{
"counter": "telegram-report-story_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} telegram-report-story stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Report a story via the multi-step option flow. First call with option:. It is categorised as a Execute tool in the MCP-Telegram MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP-Telegram MCP server in PolicyLayer and add a rule for telegram-report-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-report-story is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the telegram-report-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-report-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-report-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.