send_telegram_message
AI agents use send_telegram_message to create or update resources in Simple MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Simple MCP environment.
This tool creates/sends data (a message) to Telegram, which is reversible (messages can be deleted). It does not move money, execute arbitrary code, or irreversibly delete data. However, it can spam or leak information if misused, hence medium severity. The empty description lowers confidence slightly, but the function name is unambiguous.
From the tool's definition Tool name is 'send_telegram_message' which sends a message to Telegram. The description is empty, but the name clearly indicates a write operation that creates a message in an external service.
Attacks that exploit this kind of access
send_telegram_message. It is categorised as a Write tool in the Simple MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Simple MCP server in PolicyLayer and add a rule for send_telegram_message: 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 Simple MCP. Nothing to install.
send_telegram_message 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 send_telegram_message 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_telegram_message. 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_telegram_message is provided by the Simple MCP server (karar-hayder/simple-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →