AI agents use update_profile to create or update resources in Telegram MCP Complete — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Telegram MCP Complete environment.
The tool creates or modifies profile data, which is characteristic of Write category. It is reversible (profile can be updated again), so not Destructive. Severity is medium because unauthorized profile modification could enable impersonation, phishing, or social engineering, but the blast radius is limited to account metadata rather than mass data deletion or financial impact.
From the tool's definition Tool name 'update_profile' and description indicating profile modification ('更新你的个人资料' = 'Update your profile'). This modifies user account metadata reversibly.
Documented attack patterns abuse exactly the kind of access update_profile gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Telegram MCP Complete, and nothing reaches the server without passing your rules. This is the rule we recommend for update_profile:
{
"version": "1",
"default": "deny",
"tools": {
"update_profile": {
"limits": [
{
"counter": "update_profile_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_profile 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.
Free to start. No card required.
更新你的个人资料. It is categorised as a Write tool in the Telegram MCP Complete MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Telegram MCP Complete 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 Telegram MCP Complete. 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 Telegram MCP Complete MCP server (you922/telegram-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Telegram MCP Complete, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
153 Telegram MCP Complete tools catalogued and risk-classified — across an index of 43,000+ MCP servers.