Update the sending schedule for a specific campaign including timing, frequency, and delivery windows.
AI agents use smartlead_update_campaign_schedule to create or update resources in SmartLead MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SmartLead MCP Server environment.
This is a Write operation because it modifies campaign settings (schedule, timing, frequency, delivery windows) that can be reversed or edited. However, severity is elevated to 'high' because unintended schedule changes could disrupt active email campaigns, affect business operations, and impact lead outreach strategy at scale.
From the tool's definition The tool updates campaign schedule including timing, frequency, and delivery windows—modifying campaign configuration settings in a reversible manner.
Documented attack patterns abuse exactly the kind of access smartlead_update_campaign_schedule gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SmartLead MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for smartlead_update_campaign_schedule:
{
"version": "1",
"default": "deny",
"tools": {
"smartlead_update_campaign_schedule": {
"limits": [
{
"counter": "smartlead_update_campaign_schedule_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}smartlead_update_campaign_schedule 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.
Update the sending schedule for a specific campaign including timing, frequency, and delivery windows. It is categorised as a Write tool in the SmartLead MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SmartLead MCP Server MCP server in PolicyLayer and add a rule for smartlead_update_campaign_schedule: 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 SmartLead MCP Server. Nothing to install.
smartlead_update_campaign_schedule 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 smartlead_update_campaign_schedule 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 smartlead_update_campaign_schedule. 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.
smartlead_update_campaign_schedule is provided by the SmartLead MCP Server MCP server (leadmagic/smartlead-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SmartLead MCP Server, 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.
116 SmartLead MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.