AI agents use invite_to_chat 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.
This tool creates a new membership relationship between a user and a chat group—a reversible data modification. It does not execute arbitrary code, delete data irreversibly, or move money. The blast radius is moderate: an agent could spam invitations, add unwanted users to sensitive groups, or cause social friction, but the action can be undone by removing users.
From the tool's definition Tool name 'invite_to_chat' and description '邀请用户加入群组' (invite user to join group) directly modify group membership by adding users to chats.
Documented attack patterns abuse exactly the kind of access invite_to_chat 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 invite_to_chat:
{
"version": "1",
"default": "deny",
"tools": {
"invite_to_chat": {
"limits": [
{
"counter": "invite_to_chat_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}invite_to_chat 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 invite_to_chat: 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.
invite_to_chat 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 invite_to_chat 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 invite_to_chat. 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.
invite_to_chat 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.