schedule_telegram_message · Simple MCP: Risk & Policy

WHAT IT DOES

What schedule_telegram_message does on Simple MCP

AI agents invoke schedule_telegram_message to trigger actions in Simple MCP. 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.

WHY IT NEEDS A POLICY

Why schedule_telegram_message needs a policy

The tool name suggests it schedules a Telegram message to be sent at a future time, which triggers an external operation (sending a message via Telegram). This falls under Execute as it initiates an external communication action. Severity is high because a misused agent could send arbitrary messages to Telegram contacts/channels.

From the tool's definition Tool name 'schedule_telegram_message' combined with server description mentioning 'Telegram integration' and 'job scheduling'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

schedule_telegram_message Rate-limited

schedule_telegram_message 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "schedule_telegram_message": {
      "limits": [
        {
          "counter": "schedule_telegram_message_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Simple MCP, so you can run agents against it safely.

FAQ

Questions about schedule_telegram_message

What does the schedule_telegram_message tool do? +

schedule_telegram_message. It is categorised as a Execute tool in the Simple MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on schedule_telegram_message? +

Register the Simple MCP server in PolicyLayer and add a rule for schedule_telegram_message: 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 Simple MCP. Nothing to install.

What risk level is schedule_telegram_message? +

schedule_telegram_message is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit schedule_telegram_message? +

Yes. Add a rate_limit block to the schedule_telegram_message 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 schedule_telegram_message completely? +

Set action: deny in the PolicyLayer policy for schedule_telegram_message. 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 schedule_telegram_message? +

schedule_telegram_message is provided by the Simple MCP server (karar-hayder/simple-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.