Schedule a draft to publish at a future datetime.
AI agents use schedule_draft to create or update resources in Substack — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Substack environment.
This tool creates or modifies data reversibly. Scheduling a draft changes its metadata and triggers a future publication action, which is a form of data modification. Although it affects content distribution, the action is not destructive (can be unscheduled) and not immediately executing the publish action itself.
From the tool's definition Tool description states 'Schedule a draft to publish at a future datetime.' This modifies the state of a draft (sets a publication schedule) in a reversible manner via the sibling tool 'unschedule_draft'.
Documented attack patterns abuse exactly the kind of access schedule_draft gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Substack, and nothing reaches the server without passing your rules. This is the rule we recommend for schedule_draft:
{
"version": "1",
"default": "deny",
"tools": {
"schedule_draft": {
"limits": [
{
"counter": "schedule_draft_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}schedule_draft 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.
Free to start. No card required.
Schedule a draft to publish at a future datetime. It is categorised as a Write tool in the Substack MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Substack MCP server in PolicyLayer and add a rule for schedule_draft: 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 Substack. Nothing to install.
schedule_draft 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 schedule_draft 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 schedule_draft. 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.
schedule_draft is provided by the Substack MCP server (nanameru/substack-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Substack, 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.
11 Substack tools catalogued and risk-classified — across an index of 43,000+ MCP servers.