post_telegram
⚠ POSTS PUBLICLY & IRREVERSIBLY: send a message to a Telegram chat via YOUR bot token (BYOK). Rate-limited. dry_run to preview. Returns {ok, posted}.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/post-telegram.md
What post_telegram does on Gateway
AI agents use post_telegram to create or update resources in Gateway, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gateway environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
text | string | Yes | the message to send (max 3000) |
handle | string | — | your handle (rate limiting) |
chat_id | string | Yes | target chat id (or @channelusername) |
dry_run | boolean | — | preview, don't send |
bot_token | string | Yes | your Telegram bot token |
Parameters from the server's own tool schema.
Why post_telegram is rated Medium
This tool sends messages to a Telegram chat, which is a Write action (creating/posting content). Although the description says 'IRREVERSIBLY', the irreversibility here refers to the public visibility of the message once sent (it cannot be unsent or retracted automatically), not data destruction.
From the tool's definition 'send a message to a Telegram chat via YOUR bot token' and 'POSTS PUBLICLY & IRREVERSIBLY'
Attacks that exploit this kind of access
The rule that runs post_telegram safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For post_telegram, this is the rule to start with:
post_telegram 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every post_telegram call is checked against it from then on.
Questions about post_telegram
⚠ POSTS PUBLICLY & IRREVERSIBLY: send a message to a Telegram chat via YOUR bot token (BYOK). Rate-limited. dry_run to preview. Returns {ok, posted}. It is categorised as a Write tool in the Gateway MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
post_telegram accepts 5 parameters: text, handle, chat_id, dry_run, bot_token. Required: text, chat_id, bot_token. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for post_telegram: 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 Gateway. Nothing to install.
post_telegram 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 post_telegram 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 post_telegram. 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.
post_telegram is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue