Установить описание чата (about/bio).
AI agents use edit_chat_about 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.
This tool modifies chat properties by setting or updating the chat's description/bio field. This is a reversible write operation that changes metadata without deleting data or executing arbitrary code. Severity is medium because unauthorized modification of chat descriptions could mislead members or deface group information, but the impact is contained to metadata and easily recoverable.
From the tool's definition Tool name 'edit_chat_about' and description 'Установить описание чата (about/bio)' indicate modifying chat metadata (description/about field).
Attacks that exploit this kind of access
Установить описание чата (about/bio). 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 edit_chat_about: 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.
edit_chat_about 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 edit_chat_about 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 edit_chat_about. 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.
edit_chat_about 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 →