send_scheduled_now · Claudegram MCP: Risk & Policy

WHAT IT DOES

What send_scheduled_now does on Claudegram

AI agents invoke send_scheduled_now to trigger actions in Claudegram. 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 send_scheduled_now needs a policy

This tool forces immediate dispatch of previously scheduled Telegram messages, triggering an external send operation. The effect depends on what messages are queued and who the recipients are, making it Execute. Severity is high because an AI agent could inadvertently send messages to arbitrary contacts before the user intended, with social/reputational consequences that are difficult to reverse.

From the tool's definition 'Принудительно отправить отложенные сообщения сейчас' (Force send scheduled messages now) — triggers external messaging operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

send_scheduled_now Rate-limited

send_scheduled_now 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": {
    "send_scheduled_now": {
      "limits": [
        {
          "counter": "send_scheduled_now_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 Claudegram, so you can run agents against it safely.

FAQ

Questions about send_scheduled_now

What does the send_scheduled_now tool do? +

Принудительно отправить отложенные сообщения сейчас. It is categorised as a Execute tool in the Claudegram MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on send_scheduled_now? +

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

What risk level is send_scheduled_now? +

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

Can I rate-limit send_scheduled_now? +

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

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

send_scheduled_now is provided by the Claudegram MCP server (sanjar-x/claudegram). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.