AI agents invoke send_bot_command to trigger actions in Telegram MCP Complete. 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.
Sending bot commands triggers external operations on Telegram bots; the effects are determined by the command argument and can range from benign (/help) to significant (/start initiating workflows, or arbitrary bot-specific commands). This is an Execute action because it invokes external operations with variable effects, not merely reading or writing data.
From the tool's definition 发送机器人命令（如 /start /help）— sends bot commands such as /start and /help, triggering external bot operations whose effects depend on the command sent
Documented attack patterns abuse exactly the kind of access send_bot_command gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Telegram MCP Complete, and nothing reaches the server without passing your rules. This is the rule we recommend for send_bot_command:
{
"version": "1",
"default": "deny",
"tools": {
"send_bot_command": {
"limits": [
{
"counter": "send_bot_command_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}send_bot_command 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.
发送机器人命令（如 /start /help）. It is categorised as a Execute tool in the Telegram MCP Complete MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Telegram MCP Complete MCP server in PolicyLayer and add a rule for send_bot_command: 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 Telegram MCP Complete. Nothing to install.
send_bot_command 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 send_bot_command 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 send_bot_command. 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.
send_bot_command is provided by the Telegram MCP Complete MCP server (you922/telegram-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Telegram MCP Complete, 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.
153 Telegram MCP Complete tools catalogued and risk-classified — across an index of 43,000+ MCP servers.