create_schedule_preset
Save a scheduling_config under a name so later campaigns can reuse it. Names are unique per workspace. Set is_default to pre-fill it on new campaigns. Applying a preset copies it — later edits never retime a running campaign.
This record as markdown: /tools/digital-crew-technologies-max-mcp-server/create-schedule-preset.md
What create_schedule_preset does on Max MCP Server
AI agents use create_schedule_preset to create or update resources in Max MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Max MCP Server environment.
Why create_schedule_preset is rated Medium
This tool creates or persists new scheduling preset configurations, which is a reversible data modification (Write category). The severity is medium because misconfiguration could affect campaign timing across multiple future campaigns, but the action is fully reversible (presets can be edited or deleted) and does not permanently destroy data, execute arbitrary code, or affect financial transactions.
From the tool's definition The tool 'create_schedule_preset' has description stating 'Save a scheduling_config under a name' and 'Set is_default to pre-fill it on new campaigns', indicating it creates and stores new configuration data in the workspace.
Attacks that exploit this kind of access
The rule that runs create_schedule_preset safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Max MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_schedule_preset, this is the rule to start with:
create_schedule_preset 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Max MCP Server, apply this rule, and every create_schedule_preset call is checked against it from then on.
Questions about create_schedule_preset
Save a scheduling_config under a name so later campaigns can reuse it. Names are unique per workspace. Set is_default to pre-fill it on new campaigns. Applying a preset copies it — later edits never retime a running campaign. It is categorised as a Write tool in the Max MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Max MCP Server MCP server in PolicyLayer and add a rule for create_schedule_preset: 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 Max MCP Server. Nothing to install.
create_schedule_preset 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 create_schedule_preset 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 create_schedule_preset. 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.
create_schedule_preset is provided by the Max MCP Server MCP server (digital-crew-technologies/max-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Max MCP Server, and thousands of servers like it.
This server
Across the catalogue