reschedule_message · TrekMail MCP Server MCP: Risk & Policy

WHAT IT DOES

What reschedule_message does on TrekMail MCP Server

AI agents use reschedule_message to create or update resources in TrekMail MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TrekMail MCP Server environment.

WHY IT NEEDS A POLICY

Why reschedule_message needs a policy

This tool modifies an existing scheduled message's delivery time — a reversible write operation. It does not send a new message, delete anything, execute code, or involve financial transactions. Misuse could cause messages to be delivered at unintended times, hence medium severity.

From the tool's definition Change the delivery time of a pending scheduled message without re-sending... it does not consume a messages:send rate-limit slot.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reschedule_message Rate-limited

reschedule_message stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "reschedule_message": {
      "limits": [
        {
          "counter": "reschedule_message_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about reschedule_message

What does the reschedule_message tool do? +

Change the delivery time of a pending scheduled message without re-sending. Use this instead of cancel + schedule when the user only wants to move the send time — it does not consume a messages:send rate-limit slot. It is categorised as a Write tool in the TrekMail MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on reschedule_message? +

Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for reschedule_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 TrekMail MCP Server. Nothing to install.

What risk level is reschedule_message? +

reschedule_message is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit reschedule_message? +

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

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

reschedule_message is provided by the TrekMail MCP Server MCP server (trekmail/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

reschedule_message is one line of TrekMail MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →