# connect_bot_inbox

Explicit registration only after approval of Bot, destinations and retention. Requires separately configured receiver scope. Preserves existing webhooks and backlog, never drops messages. On uncertain result inspect before retrying. Vault Bot webhook permissions remain denied.

Agent View of the PolicyLayer registry record for `connect_bot_inbox`. HTML page: https://policylayer.com/tools/cyuanxv-telegram-bot-mcp-server/connect-bot-inbox

## Facts

- Tool: `connect_bot_inbox`
- 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: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

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

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

## Why connect_bot_inbox is rated Medium

An AI agent can call connect_bot_inbox faster than any human can review: one bad instruction and it creates or modifies resources in Telegram Bot by the hundred, each call as confident as the last.

## Use case

AI agents use connect_bot_inbox to create or update resources in Telegram Bot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Telegram Bot environment.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "connect_bot_inbox": {
      "limits": [
        {
          "counter": "connect_bot_inbox_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## 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_business_notices` — Read — https://policylayer.com/tools/cyuanxv-telegram-bot-mcp-server/read-business-notices.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_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