Schedule a draft for publishing at a specific date and time.
AI agents use schedule_draft to create or update resources in SoManyLemons MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SoManyLemons MCP environment.
Scheduling content for future publication is a write operation that creates or modifies metadata (publish date/time) associated with existing draft content. It is reversible (the schedule can be changed or canceled before publication), so it does not qualify as Destructive.
From the tool's definition Tool description states 'Schedule a draft for publishing' which modifies the state of a draft by setting a publication schedule. This is a reversible creation/modification action (scheduling is editable/cancellable).
Attacks that exploit this kind of access
Schedule a draft for publishing at a specific date and time. It is categorised as a Write tool in the SoManyLemons MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SoManyLemons 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 SoManyLemons MCP. 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 SoManyLemons MCP server (nomiddleinc/somanylemons-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →