AI agents use smartlead_update_campaign_schedule to create or update resources in Smartlead Mcp Server Sse — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Smartlead Mcp Server Sse environment.
This tool modifies campaign scheduling parameters reversibly—the changes can be undone by updating the schedule again. It does not delete data (Destructive), execute arbitrary code (Execute), or involve financial transactions (Financial).
From the tool's definition Tool name 'smartlead_update_campaign_schedule' combined with 'Update a campaign' in description indicates modification of existing campaign configuration.
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 Sse, 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 a campaign\. It is categorised as a Write tool in the Smartlead Mcp Server Sse MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Smartlead Mcp Server Sse 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 Sse. 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 Sse MCP server (jacob-dietle/smartlead-mcp-server-sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Smartlead Mcp Server Sse, 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.
15 Smartlead Mcp Server Sse tools catalogued and risk-classified — across an index of 43,000+ MCP servers.