send_sticker_by_id · Claudegram MCP: Risk & Policy

WHAT IT DOES

What send_sticker_by_id does on Claudegram

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

WHY IT NEEDS A POLICY

Why send_sticker_by_id needs a policy

This tool creates a new message in a Telegram conversation by sending a sticker. While sending stickers is reversible (messages can be deleted and edited in Telegram), it is fundamentally a write operation that modifies chat state. It does not execute arbitrary code, delete data irreversibly, or involve financial transactions.

From the tool's definition Tool name 'send_sticker_by_id' and description 'Отправить стикер по document_id' (Send sticker by document_id) indicates the tool sends/transmits content to a Telegram chat, which is a write operation that modifies the conversation state by adding a message.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

send_sticker_by_id Rate-limited

send_sticker_by_id 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": {
    "send_sticker_by_id": {
      "limits": [
        {
          "counter": "send_sticker_by_id_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 Claudegram, so you can run agents against it safely.

FAQ

Questions about send_sticker_by_id

What does the send_sticker_by_id tool do? +

Отправить стикер по document_id (получи через get_sticker_set). It is categorised as a Write tool in the Claudegram MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on send_sticker_by_id? +

Register the Claudegram MCP server in PolicyLayer and add a rule for send_sticker_by_id: 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 Claudegram. Nothing to install.

What risk level is send_sticker_by_id? +

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

Can I rate-limit send_sticker_by_id? +

Yes. Add a rate_limit block to the send_sticker_by_id 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 send_sticker_by_id completely? +

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

send_sticker_by_id is provided by the Claudegram MCP server (sanjar-x/claudegram). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.