Изменить отображаемое имя/фамилию/био собственного профиля.
AI agents use update_profile 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 creates or modifies profile metadata (name, surname, bio) reversibly. It does not delete data (not Destructive), execute arbitrary code (not Execute), move money (not Financial), or retrieve data without side effects (not Read). The modification is scoped to the user's own profile and is reversible, making it Write.
From the tool's definition Tool name 'update_profile' and description 'Изменить отображаемое имя/фамилию/био собственного профиля' (Change displayed name/surname/bio of own profile) indicate modification of profile data fields.
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 update_profile: 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.
update_profile 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 update_profile 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 update_profile. 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.
update_profile 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 →