Update account-level global privacy settings. Only pass the fields you want to change — omitted fields keep their current values. hideReadMarks and newNoncontactPeersRequirePremium require Telegram Premium.
AI agents use telegram-set-global-privacy-settings to create or update resources in MCP-Telegram — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP-Telegram environment.
This tool creates or modifies account-level privacy settings on the user's Telegram account. While the changes are reversible (settings can be modified back), the blast radius is high because misconfigured privacy settings could expose the account to unwanted contacts, disable read receipts unexpectedly, or alter security posture.
From the tool's definition Tool description states 'Update account-level global privacy settings' and 'Only pass the fields you want to change' — this directly modifies account configuration settings reversibly.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access telegram-set-global-privacy-settings gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-Telegram, and nothing reaches the server without passing your rules. This is the rule we recommend for telegram-set-global-privacy-settings:
{
"version": "1",
"default": "deny",
"tools": {
"telegram-set-global-privacy-settings": {
"limits": [
{
"counter": "telegram-set-global-privacy-settings_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}telegram-set-global-privacy-settings 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.
Update account-level global privacy settings. Only pass the fields you want to change — omitted fields keep their current values. hideReadMarks and newNoncontactPeersRequirePremium require Telegram Premium. It is categorised as a Write tool in the MCP-Telegram MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP-Telegram MCP server in PolicyLayer and add a rule for telegram-set-global-privacy-settings: 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 MCP-Telegram. Nothing to install.
telegram-set-global-privacy-settings 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 telegram-set-global-privacy-settings 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 telegram-set-global-privacy-settings. 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.
telegram-set-global-privacy-settings is provided by the MCP-Telegram MCP server (mcp-telegram/mcp-telegram). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP-Telegram, 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.
181 MCP-Telegram tools catalogued and risk-classified — across an index of 43,000+ MCP servers.