AI agents use set_bio 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.
Setting a user biography is a Write operation—it creates or modifies data reversibly. The change can be undone by setting a different bio or clearing it. It has no destructive, financial, or code-execution implications, and carries minimal blast radius if misused by an agent (limited to profile metadata).
From the tool's definition Tool name 'set_bio' and description '设置个人简介' (set personal biography) indicate the tool modifies user profile metadata. This is a reversible write operation that updates profile information without deleting data or executing code.
Documented attack patterns abuse exactly the kind of access set_bio 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 set_bio:
{
"version": "1",
"default": "deny",
"tools": {
"set_bio": {
"limits": [
{
"counter": "set_bio_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_bio 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 set_bio: 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.
set_bio 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 set_bio 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 set_bio. 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.
set_bio 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.