AI agents invoke end_call to trigger actions in Telegram MCP Complete. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Ending a call is an irreversible real-time action that affects an ongoing external communication session. It is not purely destructive (no data is deleted) but it executes an operation with immediate, hard-to-undo side effects on a live call, placing it in the Execute category.
From the tool's definition end_call / 挂断通话 (hang up a call) — triggers an external operation (terminating an active Telegram call)
Documented attack patterns abuse exactly the kind of access end_call 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 end_call:
{
"version": "1",
"default": "deny",
"tools": {
"end_call": {
"limits": [
{
"counter": "end_call_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}end_call stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
挂断通话. It is categorised as a Execute tool in the Telegram MCP Complete MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Telegram MCP Complete MCP server in PolicyLayer and add a rule for end_call: 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.
end_call is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the end_call 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 end_call. 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.
end_call 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.