AI agents use update_folder to create or update resources in Telegram — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Telegram environment.
The tool modifies folder configuration (likely renaming, reordering, or changing folder properties) rather than deleting it (Destructive) or creating it (lighter Write). Folder updates are reversible and have limited blast radius unless they affect message visibility across many chats.
From the tool's definition Tool name 'update_folder' combined with server context showing 'folder management' capabilities; sibling tools include 'create_folder' and 'delete_folder' which modify organizational state. Description is empty, reducing certainty.
Attacks that exploit this kind of access
update_folder. It is categorised as a Write tool in the Telegram MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Telegram MCP server in PolicyLayer and add a rule for update_folder: 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. Nothing to install.
update_folder 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_folder 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_folder. 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_folder is provided by the Telegram MCP server (vovavindar/telegram-mcp). 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 →