# read_business_notices

Default-disabled owner-only notification journal. Read one explicitly configured Bot and Business connection; deletion events are additionally restricted to configured chat IDs. Hides expired notices. Received order is not permission revision order. Observed enabled/rights are historical notifications, never proof of current authority. Does not read message bodies, mark messages read, send, delete or change permissions. Up to 100 deleted IDs per notice are returned with an explicit total and truncation flag.

Agent View of the PolicyLayer registry record for `read_business_notices`. HTML page: https://policylayer.com/tools/cyuanxv-telegram-bot-mcp-server/read-business-notices

## Facts

- Tool: `read_business_notices`
- Server: Telegram Bot (`@cyuanxv/telegram-bot-mcp-server`) — https://policylayer.com/tools/cyuanxv-telegram-bot-mcp-server.md
- Install: `npx -y @cyuanxv/telegram-bot-mcp-server`
- Homepage: https://www.npmjs.com/package/@cyuanxv/telegram-bot-mcp-server
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "read_business_notices",
    "arguments": {}
  }
}
```

## Why read_business_notices is rated Low

Even though read_business_notices 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.

## Use case

AI agents call read_business_notices 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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Telegram Bot:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "read_business_notices": {}
  }
}
```

## Other tools on Telegram Bot (50)

- `business` — Destructive — https://policylayer.com/tools/cyuanxv-telegram-bot-mcp-server/business.md
- `message_action` — Destructive — https://policylayer.com/tools/cyuanxv-telegram-bot-mcp-server/message-action.md
- `answer_inbox_callback` — Read — https://policylayer.com/tools/cyuanxv-telegram-bot-mcp-server/answer-inbox-callback.md
- `call_mtproto` — Read — https://policylayer.com/tools/cyuanxv-telegram-bot-mcp-server/call-mtproto.md
- `check_managed_bot_username` — Read — https://policylayer.com/tools/cyuanxv-telegram-bot-mcp-server/check-managed-bot-username.md
- `check_rich_message` — Read — https://policylayer.com/tools/cyuanxv-telegram-bot-mcp-server/check-rich-message.md
- `get_account_me` — Read — https://policylayer.com/tools/cyuanxv-telegram-bot-mcp-server/get-account-me.md
- `get_file_send_status` — Read — https://policylayer.com/tools/cyuanxv-telegram-bot-mcp-server/get-file-send-status.md
- `get_payment_order_status` — Read — https://policylayer.com/tools/cyuanxv-telegram-bot-mcp-server/get-payment-order-status.md
- `get_report_status` — Read — https://policylayer.com/tools/cyuanxv-telegram-bot-mcp-server/get-report-status.md
- `get_rich_message_status` — Read — https://policylayer.com/tools/cyuanxv-telegram-bot-mcp-server/get-rich-message-status.md
- `inspect_bot_inbox` — Read — https://policylayer.com/tools/cyuanxv-telegram-bot-mcp-server/inspect-bot-inbox.md
- `inspect_business_connection` — Read — https://policylayer.com/tools/cyuanxv-telegram-bot-mcp-server/inspect-business-connection.md
- `inspect_configuration` — Read — https://policylayer.com/tools/cyuanxv-telegram-bot-mcp-server/inspect-configuration.md
- `inspect_default_inbox` — Read — https://policylayer.com/tools/cyuanxv-telegram-bot-mcp-server/inspect-default-inbox.md
- `list_accounts` — Read — https://policylayer.com/tools/cyuanxv-telegram-bot-mcp-server/list-accounts.md
- `list_bots` — Read — https://policylayer.com/tools/cyuanxv-telegram-bot-mcp-server/list-bots.md
- `list_chats` — Read — https://policylayer.com/tools/cyuanxv-telegram-bot-mcp-server/list-chats.md
- `list_dialogs` — Read — https://policylayer.com/tools/cyuanxv-telegram-bot-mcp-server/list-dialogs.md
- `read_inbox` — Read — https://policylayer.com/tools/cyuanxv-telegram-bot-mcp-server/read-inbox.md
- `search_account_messages` — Read — https://policylayer.com/tools/cyuanxv-telegram-bot-mcp-server/search-account-messages.md
- `call_bot_api` — Write — https://policylayer.com/tools/cyuanxv-telegram-bot-mcp-server/call-bot-api.md
- `chat_admin` — Write — https://policylayer.com/tools/cyuanxv-telegram-bot-mcp-server/chat-admin.md
- `compose_daily_report` — Write — https://policylayer.com/tools/cyuanxv-telegram-bot-mcp-server/compose-daily-report.md
- `connect_bot_inbox` — Write — https://policylayer.com/tools/cyuanxv-telegram-bot-mcp-server/connect-bot-inbox.md
- `connect_default_inbox` — Write — https://policylayer.com/tools/cyuanxv-telegram-bot-mcp-server/connect-default-inbox.md
- `create_managed_bot` — Write — https://policylayer.com/tools/cyuanxv-telegram-bot-mcp-server/create-managed-bot.md
- `dispatch_report_chunk` — Write — https://policylayer.com/tools/cyuanxv-telegram-bot-mcp-server/dispatch-report-chunk.md
- `draft_payment_order` — Write — https://policylayer.com/tools/cyuanxv-telegram-bot-mcp-server/draft-payment-order.md
- `draft_report` — Write — https://policylayer.com/tools/cyuanxv-telegram-bot-mcp-server/draft-report.md
- …and 20 more: https://policylayer.com/tools/cyuanxv-telegram-bot-mcp-server.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=cyuanxv-telegram-bot-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/cyuanxv-telegram-bot-mcp-server