AI agents call delete_proxy to permanently remove resources in Telegram MCP Complete — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a proxy configuration, which cannot be undone. While the blast radius is moderate (affects only proxy settings, not user data or financial assets), the destructive nature of deletion without recovery options makes this Destructive rather than Write. Confidence is high because the name and translated description are explicit about deletion.
From the tool's definition Tool name is 'delete_proxy' and description translates to 'Delete the specified proxy configuration'. The verb 'delete' indicates irreversible removal of data.
Documented attack patterns abuse exactly the kind of access delete_proxy 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 delete_proxy:
{
"version": "1",
"default": "deny",
"hide": [
"delete_proxy"
]
}delete_proxy disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
删除指定的代理配置. It is categorised as a Destructive tool in the Telegram MCP Complete MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Telegram MCP Complete MCP server in PolicyLayer and add a rule for delete_proxy: 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.
delete_proxy is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_proxy 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 delete_proxy. 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.
delete_proxy 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.