schedule_draft · Buttondown MCP Server MCP: Risk & Policy

WHAT IT DOES

What schedule_draft does on Buttondown MCP Server

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

WHY IT NEEDS A POLICY

Why schedule_draft needs a policy

This tool modifies data (draft status/scheduling) in a reversible manner, placing it in the Write category. Severity is high because scheduling email sends can impact many recipients and affect business communications; misuse could send unwanted bulk communications. The explicit user confirmation requirement partially mitigates risk, supporting the high (rather than critical) severity rating.

From the tool's definition "Schedule an existing email draft to be sent at a specific time. This tool requires explicit user confirmation before proceeding as it will modify the draft" - the tool modifies draft state by scheduling it for sending.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

schedule_draft Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "schedule_draft": {
      "limits": [
        {
          "counter": "schedule_draft_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 Buttondown MCP Server, so you can run agents against it safely.

FAQ

Questions about schedule_draft

What does the schedule_draft tool do? +

Schedule an existing email draft to be sent at a specific time. This tool requires explicit user confirmation before proceeding as it will modify the draft. It is categorised as a Write tool in the Buttondown 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 schedule_draft? +

Register the Buttondown MCP Server 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 Buttondown MCP Server. Nothing to install.

What risk level is schedule_draft? +

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

Can I rate-limit schedule_draft? +

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.

How do I block schedule_draft completely? +

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.

What MCP server provides schedule_draft? +

schedule_draft is provided by the Buttondown MCP Server MCP server (the-focus-ai/buttondown-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.