AI agents use unmute_chat to create or update resources in Telegram — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Telegram environment.
Unmuting a chat changes user notification preferences but does not create, delete, or retrieve data. It is a reversible modification of chat metadata (notification state), placing it squarely in the Write category. The blast radius is minimal: unintended unmuting causes noise rather than data loss or financial harm. Severity is low because the user can easily re-mute the chat.
From the tool's definition Tool description states 'Unmute notifications for a chat' — this modifies chat notification settings, a reversible state change.
Attacks that exploit this kind of access
Unmute notifications for a chat. It is categorised as a Write tool in the Telegram MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Telegram MCP server in PolicyLayer and add a rule for unmute_chat: 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. Nothing to install.
unmute_chat is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the unmute_chat 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 unmute_chat. 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.
unmute_chat is provided by the Telegram MCP server (vovavindar/telegram-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →