High Risk →

telegram-toggle-anti-spam

Enable or disable aggressive anti-spam filtering in a supergroup. Supergroup only (not broadcast channels); requires admin with ban_users permission

How to control telegram-toggle-anti-spam ↓

What telegram-toggle-anti-spam does on MCP-Telegram

AI agents invoke telegram-toggle-anti-spam to trigger actions in MCP-Telegram. 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.

High Risk

Why telegram-toggle-anti-spam needs a policy

This tool toggles a moderation setting that controls anti-spam filtering in a supergroup, which can affect which messages/users are allowed or blocked. It executes a configuration change with significant impact — disabling anti-spam could expose the group to spam attacks, while enabling it could inadvertently filter legitimate users.

From the tool's definition Enable or disable aggressive anti-spam filtering in a supergroup... requires admin with ban_users permission

Risk signalsAdmin/system-level operation

Documented attack patterns abuse exactly the kind of access telegram-toggle-anti-spam gives an agent:

How to control telegram-toggle-anti-spam

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-toggle-anti-spam:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "telegram-toggle-anti-spam": {
      "limits": [
        {
          "counter": "telegram-toggle-anti-spam_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

telegram-toggle-anti-spam 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.

  1. Create a free account and register MCP-Telegram — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about telegram-toggle-anti-spam

What does the telegram-toggle-anti-spam tool do? +

Enable or disable aggressive anti-spam filtering in a supergroup. Supergroup only (not broadcast channels); requires admin with ban_users permission. It is categorised as a Execute tool in the MCP-Telegram MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on telegram-toggle-anti-spam? +

Register the MCP-Telegram MCP server in PolicyLayer and add a rule for telegram-toggle-anti-spam: 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.

What risk level is telegram-toggle-anti-spam? +

telegram-toggle-anti-spam is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit telegram-toggle-anti-spam? +

Yes. Add a rate_limit block to the telegram-toggle-anti-spam 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.

How do I block telegram-toggle-anti-spam completely? +

Set action: deny in the PolicyLayer policy for telegram-toggle-anti-spam. 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.

What MCP server provides telegram-toggle-anti-spam? +

telegram-toggle-anti-spam 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.

Enforce policy on every MCP-Telegram tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.