create_schedule
Set up the DemoStudio Agent to automatically generate and export a new video on a recurring schedule
This record as markdown: /tools/demostudio/create-schedule.md
What create_schedule does on DemoStudio
AI agents invoke create_schedule to trigger actions in DemoStudio. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why create_schedule is rated High
This tool configures an automated, recurring execution of video generation and export operations. It is not merely writing a record — it triggers external processes on a schedule, which qualifies as Execute. The severity is high because a misconfigured schedule could repeatedly consume API resources, storage, and potentially incur costs at scale, with effects that compound over time until explicitly cancelled.
From the tool's definition 'automatically generate and export a new video on a recurring schedule' — sets up a recurring automated process that triggers external operations (video generation and export) repeatedly over time
Attacks that exploit this kind of access
The rule that runs create_schedule safely
PolicyLayer is an MCP gateway: it sits between your AI agents and DemoStudio, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_schedule, this is the rule to start with:
create_schedule stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect DemoStudio, apply this rule, and every create_schedule call is checked against it from then on.
Questions about create_schedule
Set up the DemoStudio Agent to automatically generate and export a new video on a recurring schedule. It is categorised as a Execute tool in the DemoStudio MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the DemoStudio MCP server in PolicyLayer and add a rule for create_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 DemoStudio. Nothing to install.
create_schedule is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the create_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 create_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.
create_schedule is provided by the DemoStudio MCP server (@demostudio/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on DemoStudio, and thousands of servers like it.
Across the catalogue