activate_script_version
Switch the project's active script to another saved version (ids come from get_script's version list — every save_script creates one). Re-run scan_script / rescan_voice_blocks afterwards if the text differs, since downstream artifacts follow the active version.
This record as markdown: /tools/com-framesail-framesail/activate-script-version.md
What activate_script_version does on Framesail
AI agents use activate_script_version 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 |
|---|---|---|---|
script_id | string | Yes | ID of the script version to activate, from get_script's version list |
Parameters from the server's own tool schema.
Why activate_script_version is rated Medium
This tool modifies project state reversibly by switching between saved script versions. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), or trigger financial transactions (would be Financial). The change is reversible since the previous version remains saved and can be re-activated.
From the tool's definition Tool description states it will "Switch the project's active script to another saved version" and "Re-run scan_script / rescan_voice_blocks afterwards if the text differs, since downstream artifacts follow the active version." This modifies the project state…
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs activate_script_version 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 activate_script_version, this is the rule to start with:
activate_script_version 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 activate_script_version call is checked against it from then on.
Questions about activate_script_version
Switch the project's active script to another saved version (ids come from get_script's version list — every save_script creates one). Re-run scan_script / rescan_voice_blocks afterwards if the text differs, since downstream artifacts follow the active version. 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.
activate_script_version accepts 1 parameter: script_id. Required: script_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 activate_script_version: 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.
activate_script_version 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 activate_script_version 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 activate_script_version. 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.
activate_script_version 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