check_rich_message
Validate phase-one structured blocks and supplied image hashes without sending. Not native rendering.
This record as markdown: /tools/cyuanxv-telegram-bot-mcp-server/check-rich-message.md
What check_rich_message does on Telegram Bot
AI agents call check_rich_message to retrieve information from Telegram Bot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why check_rich_message is rated Low
Even though check_rich_message only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs check_rich_message safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Telegram Bot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_rich_message, this is the rule to start with:
check_rich_message is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Telegram Bot, apply this rule, and every check_rich_message call is checked against it from then on.
Questions about check_rich_message
Validate phase-one structured blocks and supplied image hashes without sending. Not native rendering. It is categorised as a Read tool in the Telegram Bot MCP Server, which means it retrieves data without modifying state.
Register the Telegram Bot MCP server in PolicyLayer and add a rule for check_rich_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 Telegram Bot. Nothing to install.
check_rich_message is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the check_rich_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 check_rich_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.
check_rich_message is provided by the Telegram Bot MCP server (@cyuanxv/telegram-bot-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Telegram Bot, and thousands of servers like it.
This server
Across the catalogue