generate_script
Generate the project's script from its description/concept and the channel's narrative style. Async — returns {job_id}; poll get_workflow_status.
This record as markdown: /tools/com-framesail-framesail/generate-script.md
What generate_script does on Framesail
AI agents use generate_script to create or update resources in Framesail, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Framesail environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
model | string | — | Model ID to generate with; empty uses the default (see list_models("script")) |
settings | object | — | Model-specific settings; valid keys come from the model's settings_schema in list_models("script") |
project_id | string | Yes | Project ID, as returned by create_project or list_projects |
editable_sections | object | — | Per-call prompt section overrides, keyed by section name; see get_section_template("script") for the sections this job exposes |
Parameters from the server's own tool schema.
Why generate_script is rated Medium
This tool creates new content (a script) based on input parameters. It is a Write operation — it produces and stores a script artifact for the project. It is not Destructive, Financial, or Execute (no code/commands run; it triggers an async generation job, but the output is a content artifact). Severity is medium because a misused script generation could produce inappropriate or misleading content at scale.
From the tool's definition Generate the project's script from its description/concept and the channel's narrative style. Async — returns {job_id}
Attacks that exploit this kind of access
The rule that runs generate_script safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Framesail, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For generate_script, this is the rule to start with:
generate_script 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 Framesail, apply this rule, and every generate_script call is checked against it from then on.
Questions about generate_script
Generate the project's script from its description/concept and the channel's narrative style. Async — returns {job_id}; poll get_workflow_status. It is categorised as a Write tool in the Framesail MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
generate_script accepts 4 parameters: model, settings, project_id, editable_sections. Required: project_id. The full parameter table on this page comes from the server's own tool schema.
Register the Framesail MCP server in PolicyLayer and add a rule for generate_script: 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 Framesail. Nothing to install.
generate_script 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 generate_script 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 generate_script. 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.
generate_script is provided by the Framesail MCP server (https://api.framesail.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Framesail, and thousands of servers like it.
This server
Across the catalogue