reschedule_message
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.
This record as markdown: /tools/trekmail-mcp-server/reschedule-message.md
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 reschedule_message is rated Medium
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
The rule that runs reschedule_message safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TrekMail MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For reschedule_message, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect TrekMail MCP Server, apply this rule, and every reschedule_message call is checked against it from then on.
Questions about reschedule_message
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.
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.
reschedule_message is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
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.
More on TrekMail MCP Server, and thousands of servers like it.
This server
Across the catalogue