Вернуть диалог из архива в основной список (folder=0).
AI agents use unarchive_dialog 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.
The tool changes the folder/organizational state of a Telegram dialog but does not delete data or execute external code. It is reversible (can be re-archived), making it a Write action rather than Destructive. The severity is medium because misuse could reorganize a user's chat structure, creating confusion or visibility of private conversations, but the action is easily undone.
From the tool's definition Tool description states 'Вернуть диалог из архива в основной список (folder=0)' — translates to 'Return dialog from archive to main list' — which modifies the state/organization of a chat dialog by moving it from archived status to active status.
Attacks that exploit this kind of access
Вернуть диалог из архива в основной список (folder=0). 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.
Register the Claudegram MCP server in PolicyLayer and add a rule for unarchive_dialog: 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.
unarchive_dialog 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 unarchive_dialog 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 unarchive_dialog. 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.
unarchive_dialog 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.
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 →