telegram_send_dice | PolicyLayer

WHAT IT DOES

What telegram_send_dice does on Telegram MCP Server & Channel Monitor

AI agents use telegram_send_dice to create or update resources in Telegram MCP Server & Channel Monitor — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Telegram MCP Server & Channel Monitor environment.

WHY IT NEEDS A POLICY

Why telegram_send_dice needs a policy

Sending dice or slot animations to a Telegram chat modifies the chat state by adding new messages, which is a Write operation. The severity is low because: (1) the action is reversible (messages can be deleted), (2) it has minimal blast radius (no access to sensitive data, financial operations, or system commands), and (3) the effect is benign and cosmetic.

From the tool's definition The tool description states it sends random animations (dice/slot) to Telegram chats. 'Send' is a write operation that creates new content in a chat without reversibility concerns or destructive effects.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

telegram_send_dice Rate-limited

telegram_send_dice stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "telegram_send_dice": {
      "limits": [
        {
          "counter": "telegram_send_dice_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Telegram MCP Server & Channel Monitor, so you can run agents against it safely.

FAQ

Questions about telegram_send_dice

What does the telegram_send_dice tool do? +

텔레그램 채팅에 주사위/슬롯 등 랜덤 애니메이션을 전송합니다. It is categorised as a Write tool in the Telegram MCP Server & Channel Monitor MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on telegram_send_dice? +

Register the Telegram MCP Server & Channel Monitor MCP server in PolicyLayer and add a rule for telegram_send_dice: 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 Server & Channel Monitor. Nothing to install.

What risk level is telegram_send_dice? +

telegram_send_dice is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit telegram_send_dice? +

Yes. Add a rate_limit block to the telegram_send_dice 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.

How do I block telegram_send_dice completely? +

Set action: deny in the PolicyLayer policy for telegram_send_dice. 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.

What MCP server provides telegram_send_dice? +

telegram_send_dice is provided by the Telegram MCP Server & Channel Monitor MCP server (ruchiayeon/telegram-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.