AI agents use contactsAliasSet to create or update resources in Telegram MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Telegram MCP Server environment.
This tool modifies contact metadata (aliases) in a reversible manner. It creates or updates an alias record without deleting data or executing arbitrary code. The moderate severity reflects that an agent could mislead users by setting deceptive aliases, but the change can be undone. Not higher severity because the impact is scoped to contact metadata only.
From the tool's definition Tool name 'contactsAliasSet' and description 'Sets an alias for a contact' indicate creation or modification of contact data. The action is reversible (aliases can be changed or removed via sibling tool contactsAliasRemove).
Documented attack patterns abuse exactly the kind of access contactsAliasSet gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Telegram MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for contactsAliasSet:
{
"version": "1",
"default": "deny",
"tools": {
"contactsAliasSet": {
"limits": [
{
"counter": "contactsaliasset_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}contactsAliasSet 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.
Sets an alias for a contact. It is categorised as a Write tool in the Telegram MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Telegram MCP Server MCP server in PolicyLayer and add a rule for contactsAliasSet: 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 Server. Nothing to install.
contactsAliasSet 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 contactsAliasSet 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 contactsAliasSet. 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.
contactsAliasSet is provided by the Telegram MCP Server MCP server (kfastov/tgcli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Telegram MCP Server, 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.
38 Telegram MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.