telegram_unpin_message
Unpin a message in a chat
This record as markdown: /tools/io-github-alifanov-scopegate/telegram-unpin-message.md
What telegram_unpin_message does on ScopeGate
AI agents use telegram_unpin_message to create or update resources in ScopeGate, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ScopeGate environment.
Why telegram_unpin_message is rated Medium
Unpinning a message modifies the chat state by removing a pinned message designation. This is a reversible action (the message can be pinned again), so it falls under Write rather than Destructive. Misuse could disrupt communication in group chats by removing important pinned messages, hence medium severity.
From the tool's definition Unpin a message in a chat
Attacks that exploit this kind of access
The rule that runs telegram_unpin_message safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For telegram_unpin_message, this is the rule to start with:
telegram_unpin_message 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.
The button opens the PolicyLayer dashboard: create your workspace, connect ScopeGate, apply this rule, and every telegram_unpin_message call is checked against it from then on.
Questions about telegram_unpin_message
Unpin a message in a chat. It is categorised as a Write tool in the ScopeGate MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ScopeGate MCP server in PolicyLayer and add a rule for telegram_unpin_message: 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 ScopeGate. Nothing to install.
telegram_unpin_message 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 telegram_unpin_message 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 telegram_unpin_message. 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.
telegram_unpin_message is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScopeGate, and thousands of servers like it.
This server
Across the catalogue