Закрепить/открепить диалог в шапке списка.
AI agents use pin_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.
Pinning/unpinning a dialog modifies the state of the user's chat interface—specifically reordering which conversations appear at the top of the list. This is a reversible Write operation: the user can unpin dialogs to restore previous state. It does not retrieve data (Read), execute code (Execute), permanently delete data (Destructive), or involve financial transactions (Financial).
From the tool's definition The tool name 'pin_dialog' and description 'Закрепить/открепить диалог в шапке списка' (Pin/unpin dialog in the chat list header) indicate modification of user interface state and chat organization metadata.
Attacks that exploit this kind of access
Закрепить/открепить диалог в шапке списка. 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 pin_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.
pin_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 pin_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 pin_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.
pin_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 →